The RabbitMQ team announced the release of RabbitMQ 3.6.11.
Binary and source distributions of the new release can be found on the downloads page, GitHub, Package Cloud, and Bintray.
The Apache Software Foundation released Apache ActiveMQ Artemis 2.2.0.
Release notes: https://activemq.apache.org/artemis/release-notes-2.2.0.html
Documentation: https://activemq.apache.org/artemis/docs.html
About Apache ActiveMQ Artemis:
The Apache ActiveMQ Artemis message broker includes AMQP protocol support, OpenWire support for ActiveMQ 5 clients, MQTT support, STOMP protocol support, HornetQ Core protocol support for HornetQ 2.4,2.5 clients, JMS 2.0 and 1.1 support.
Apache ActiveMQ 5.15.0 has been released and includes many fixes and improvements. Also note that this release bumps the minimum required Java version to Java 8. A list of issues resolved in this release is available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338054
The Wiki page for the release is here:
http://activemq.apache.org/activemq-5150-release.html
Habarisoft released new versions of its Object Pascal STOMP client libraries for Delphi and FPC integration with popular free open source message brokers. The 2017.06 release includes
In version 5.1.0, the chat demo creates its own receive thread to listen for chat messages. It is recommended to receive messages synchronously in this way, as it allows customized handling of connection failures. Minimal source code changes to the demo program were neccessary to use the new receive thread.
The chat demo receives incoming messages in a simple thread without error handling. To recover from connection failures, the code would need a second loop which reconnects and starts the main loop again.
Connection := Factory.CreateConnection;
try
try
Connection.Start;
Session := Connection.CreateSession(amAutoAcknowledge);
Destination := Session.CreateTopic(ChatTopic);
Consumer := Session.CreateConsumer(Destination);
while not Terminated do
begin
Msg := Consumer.Receive(5000);
if Assigned(Msg) then
begin
TThread.Queue(nil, PrintMessage);
end;
end;
except
on E: Exception do
begin
// (no recovery from connection failures)
if IsConsole then WriteLn(E.Message);
end;
end;
finally
Connection.Close;
end;
The performance test program now uses the IConnectionInterface to retrieve the broker version string when running the test. In the example screenshot below, the application has connected to the “RabbitMQ 3.6.10” broker on the local machine.
You may also collect the message rates of multiple test runs and displays the sample median. To start the long-running tests, shift-click on the run button. Taking all test samples takes around ten seconds.
The example dialog now uses the IConnectionInterface to retrieve the broker version string when pinging the message broker. In the example screenshot below, the application has connected to the “RabbitMQ 3.6.10” broker on the local machine.
The DUnit and FPCUnit now use the IConnectionInfo interface to retrieve the broker version string from the running message broker. In the example shown below, the FPCUnit GUI TestRunner has connected to the “ActiveMQ/5.14.5” message broker on the local machine during the initialization of the test runner.
In the second example, the DUnit GUI TestRunner has connected to the “RabbitMQ 3.6.10” message broker on the local machine.
Unit tests use the STOMP 1.2 wire protocol now by default (Habari Client for OpenMQ still uses STOMP 1.0).
The library requires Delphi 2009 or Free Pascal 3.0.2 (or newer).
Full release notes are available at https://www.habarisoft.com/releases/2017.06/
Habari Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology – which is distributed, loosely coupled, reliable and asynchronous – to build integrated systems, using peer-to-peer and publish-subscribe communication models.
The Apache ActiveMQ Artemis message broker is planned to be the follow-on to Apache ActiveMQ, which is basically in maintenance mode. Read more about migration from ActiveMQ 5.x to Apache ActiveMQ Artemis in this user forum post.
Apache ActiveMQ Artemis is based off of HornetQ, a production broker that supported JMS. Now, Artemis is also the default messaging provider in the WildFly application server.
Habari Client libraries 2017.06 (release date TBD) includes an enhanced performance test application, which optionally collects message rates of multiple test runs and displays the sample median.
To start the long-running tests, shift-click on the run button. Taking all test samples takes around ten seconds.
Shown below is an example for a client configuration:
Server configuration:
The current product versions Habari Client for ActiveMQ 5.1.0 (tested with Apache ActiveMQ 5.14.5), Habari Client for Artemis 5.1.0 (tested with Apache ActiveMQ Artemis 2.1.0) and Habari Client for RabbitMQ 5.1.0 (tested with RabbitMQ 3.6.10) reached over 12000 messages per second in the given test environment.
The current product version Habari Client for OpenMQ 5.1.0 (tested with Open Message Queue 5.1.1) reached more than 6000 messages per second.
Errors and omissions excepted. No warranty of any sort, expressed or implied, is provided in connection with the library, including, but not limited to, implied warranties of merchantability or fitness for a particular purpose.
Habari Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology – which is distributed, loosely coupled, reliable and asynchronous – to build integrated systems, using peer-to-peer and publish-subscribe communication models.
As reported on the RabbitMQ user group, Erlang/OTP 20 is going to be released quite soon. Regarding compatibility with the current RabbitMQ message broker version and potentially breaking changes, the latest message says:
So RabbitMQ 3.6.10 should now support OTP-20 (after release). We are still testing versions 3.6.4 to 3.6.9 for compatibility.
