Apache ActiveMQ 5.12.0 resolves several issues, and provides significant improves to the AMQP and MQTT support in the broker as well as fixing issues with STOMP and MQTT over WebSockets plus much much more.
Apache ActiveMQ 5.10.0 resolves more than 234 issues, mostly bug fixes and improvements. It has the following new features:
- Java 8 support
- Apache Shiro Security Plugin – http://activemq.apache.org/shiro.html
- Hardened MQTT support
- Hardened AMQP support
- Hardened LevelDB store
- Improved RAR/JCA adapter
- Improved Runtime configuration plugin
- Improved Web console
A Delphi and Free Pascal STOMP based client library is available from Habarisoft.
Apache ActiveMQ 5.9.1 resolves more than 120 issues, mostly bug fixes and improvements. It has the following new features:
- Replicated LevelDB Store for shared nothing Master/Slave.
- Runtime Configuration
- Hawtio web console
- Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)
- MQTT over WebSockets support
- broker Apache Camel component
- Broker auto-restart upon losing master status
- AMQP Hardening
- LevelDB Hardening
A Delphi and Free Pascal client library is available from Habarisoft.
Apache ActiveMQ 5.9.0
This release addresses over 200 issues and introduces some significant improvements, for example: new hawtio web console, replicated leveldb message store, Runtime configuration. Read more …
This release introduced federated queues and features enhanced policies for aspects of the broker which previously required AMQP arguments. Clients can now obtain better feedback about authentication failures and broker alarm conditions. Read more …
GlassFish Open MQ 5.0 is the worlds first JMS 2.0 compliant messaging project. Read more …
This includes JMS 2.0, AMQP support and fixes. Read more …
Native Delphi and Free Pascal client libraries available!
The Habari Client library product line by Habarisoft uses the STOMP standard to communicate with message brokers. STOMP provides an interoperable wire format so that STOMP clients can communicate with any STOMP message broker to provide easy and widespread messaging interoperability among many languages, platforms and brokers.
This article shows how Delphi can use IP multicast to discover running Apache ActiveMQ message brokers in the local network. The code has been tested with Internet Direct (Indy) 10.6, which is the version included in Delphi XE4, and Apache ActiveMQ 5.8, which is the current release of the open source message broker.
With the code below, a Delphi application can list all ActiveMQ brokers, see their status, and get their IP address. This allows for dynamic configuration of client applications (built for example with Habari Client for ActiveMQ), where systems do not need to know the location of message brokers. It also allows automatic handling of broker failures or maintenance windows without intervention.
The output shows that a broker was found, running on the computer ‘my-PC’. The URL part indicates that the broker provides a connector for the OpenWire protocol on port 61616.
Waiting for broker discovery messages ... Brokers found: default.ActiveMQ-4.alive.%localhost%tcp://my-PC:61616
GlassFish 4 – the first Java EE 7 application server – has been released. It is open source and available for download here – in two versions (Full Java EE platform and the Java EE Web Profile with reduced resource footprint) for Windows, Solaris, Linux and OS X.
New features include standardized API support for the WebSocket (JSR 356) and JSON (JSR 353) specifications, HTML5 support in the JavaServer Faces version 2.2, JMS 2.0, a Batch processing API (JSR 352), Concurrency support, and more. See also: GlassFish 4 Brings Java EE 7
Delphi and Free Pascal applications can be integrated in GlassFish (Full Java EE platform) web applications and web services using the Habari Client libraries from Habarisoft, which provide direct communication with the Open Message Queue (Open MQ) message broker, which is the default JMS provider in GlassFish 3 and 4.
This article shows the code for a Delphi server which receives a RPC call message from the inbound RabbitMQ request queue, and sends the response message back to the Java client. It is the mirror code for the previous article.
The RabbitMQ online tutorial Remote procedure call (RPC) – using the Java client demonstrates how RPC can be implemented between a Java client and a Java server process, communicating over the RabbitMQ open source message broker.
But access to the RPC server process is not limited to Java applications – Delphi and Free Pascal applications using the Habari Client for RabbitMQ library can invoke the server process method too.
This article shows the code for a Delphi client which sends a RPC call message to the inbound RabbitMQ request queue, and receives the response message over a temporary queue, which exists only for the duration of the connection.
- Home page: http://www.habarisoft.com/habari_apollo.html
- Documentation (PDF): http://www.habarisoft.com/download/HabariApolloGettingStarted.pdf
- API documentation (HTML): http://www.habarisoft.com/habari_apollo/1.3/docs/api/index.html
Habari Client libraries provide access to production-ready and industry standard based cross-platform application integration, using the peer-to-peer or the publish/subscribe communication model. They are available for the open source message brokers ActiveMQ, Apollo, HornetQ, OpenMQ and RabbitMQ.