The second release candidate of version 10.3 of the Habari STOMP Client libraries for Delphi and Free Pascal is now available for ActiveMQ, Artemis, OpenMQ and RabbitMQ. Since RC1, we found and fixed four defects that every application can run into: a transacted session could lose its work without an error, a short receive time-out could cut a frame short when a consumer works off a backlog, heart-beats were checked although the broker had declined them, and newer mORMot 2 versions hid a closed connection. Because these fixes change code that every connection goes through, we would like you to test them before the final release in December.
Fixed since RC1
- Transactions: a transacted session no longer loses its work when the connection is started again. Every
Starton a started connection began a new transaction and left the open one behind, soCommitcommitted nothing of what came before. With the simplified API this happened on everyCreateProducerandCreateConsumerof a transacted context: twoContext.CreateProducer.Send(...)calls in one transaction committed only the second message.Starton a started connection now does nothing, as documented. Version 10.2 behaved the same, so please check transacted code paths with this candidate. - Receiving under load:
ReceiveNoWaitandReceivewith a short time-out no longer cut a frame short when its rest arrives late, for example while a consumer works off a backlog. The message was broken or lost, and the next read failed with “Invalid trailing END_SEP byte”. Once a frame has started, the rest is now read with the frame data time-out. Affects all three communication adapters. - Heart-beats: when the broker declines heart-beats in one direction (OpenMQ answers
heart-beat:0,0), the client no longer expects them, soCheckHeartbeatno longer raises “Heartbeat too late” there. - mORMot 2:
Receiveraises an exception when the broker closes the connection also with mORMot 2 versions after2.4-stable. Tested with2.4-stableand with 2.4.17677.
Please note
- Persistent messages always wait for a receipt. A message sent with
dmPersistentrequests a receipt even withoutsend.receipt=true, so the known receipt limitation applies to it as well. WithHABARI_BROKEN_MESSAGELISTENERdefined, don’t send persistent messages on a connection that has a message listener; use a separate connection or context. The guide’s listener chapter now says so. - Demo zip: HabariChat is no longer in the demo zip. HabariChatRooms shows the same chat, with
IMessageListenerinstead of a read thread of its own. The HabariChat source is still installed with the other demos. - The known issues of RC1 are unchanged; they are listed in the release notes and the guide.
- This is a release candidate, so please don’t use it in production yet.
Tested with ActiveMQ 6.3.2 and 6.4.0, Artemis 2.57.0, OpenMQ 6.9.0, RabbitMQ 4.4.0 and Indy 10.6.3.15.
The full release notes are at https://www.habarisoft.com/release_notes.html#r2026.12.
How to get it: registered users can download the release candidate from the usual download area now; the product pages at https://www.habarisoft.com/ link to it.
Feedback: please send reports and questions to info@habarisoft.com by 26 November 2026, so we can include fixes in the final release.