lroloson wrote:
The Broker built from trunk rev 80239 and the 3rd part persistence from rev
3353 seem to send the messages in order when the connection is broken and
then reestablished. The problems I noticed with the 0.5 release seem to be
resolved at this level.
Great! Thanks for the update. I believe this is due to the ability for
the broker to detect the failed connection faster now that it tracks
heartbeats as well as the client.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
