With the current release of Habari Client for HornetQ, Delphi and Free Pascal applications can send messages to a HornetQ message broker at a rate of more than 11000 to 12000 messages per second (less than 80 microseconds per message) – on very modest hardware and running the HornetQ server on the same system, even while receiving more than 1000 messages per second from the same broker.
The next release will introduce support for STOMP level 1.2 and the HornetQ 2.3.0 open source message broker.
The next release of the Delphi and Free Pascal library Habari Client for HornetQ passed tests with HornetQ 2.3.0.CR2 in STOMP 1.2 protocol mode. In STOMP 1.2, message acknowledgment has been simplified and now uses a dedicated header.
April 2, 2013 – Habarisoft is pleased to announce release 2.0 of Habari Client for HornetQ. HornetQ is an open source project from the JBoss Community to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. HornetQ is the default Java Message Service (JMS) provider in JBoss Application Server, but can also used stand-alone.
This library provides Delphi and Free Pascal developers access to production-ready and industry standard based cross-platform application integration, using the peer-to-peer or the publish/subscribe communication model.
Updating Internet Direct (Indy) 10 component packages in the Delphi IDE to a newer version is quite time-consuming. Doing backups, searching and removing old source and binary files, changing IDE paths – all these steps cause developers to think twice before trying a new release of the Indy library. Quick switching between versions – to do a quick compatibility test – would be very welcome.
But there is a solution – runtime creation of components. Then, instead of installing the new component versions in the IDE palette, just add the Indy library paths to the project or IDE library search path(s).
The next release of Habari message broker client libraries includes an example for automatic reconnect in case of connection loss.
It uses two nested loops, where the outer loop connects and disconnects, and the inner loops processes (sends or receives) messages. If an exception occurs while sending or receiving data on the TCP socket, the program leaves the inner loop, closes the connection and restarts the outer loop.
From the launchpad details, the rabbitmq-server included in Ubuntu 13.04 will be at least v3.0.2-1. From the release schedule the final freeze is upon us so it is unlikely that any newer version will be included.
The next major versions of Habari message broker client libraries for Delphi and Free Pascal are close to release. The new versions introduce options for easier detection of connection loss, reduced resource usage for synchronous operation mode, improved support for heart-beating (on STOMP 1.1 capable message brokers), source code refactorings, and have been tested with the open source message brokers Apache ActiveMQ 5.8.0, Apollo 1,6, HornetQ 2.3.0.CR1, OpenMQ 4.5.3 and RabbitMQ 3.0.4.
JBoss A-MQ is intended as a “lightweight” alternative to Red Hat’s own Enterprise Service Bus (ESB) and used to be known as Fuse Message Broker. The technology is mainly based on the Apache ActiveMQ messaging platform.