On 01/08/2014 02:32 PM, uromahn wrote:
Final update: this is not a bug in the AMQP 1-0 JMS client but rather a
"feature". Turns out that the AMQP client uses async publishing by default
boosting the performance but violating the delivery guarantee of persistent
messages.

However, when using the sync publishing mode, it appears that the amqp
client has another bug which makes it extremely slow and hence practically
unusable.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Interesting-Persistent-Messaging-Performance-tp4676001p4676129.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Patches have been applied to both ActiveMQ trunk and to the QPid AMQP JMS client code that should address the sync send issue. Messages that are sent with the persistent flag set outside of a TX should now be sent synchronously and the broker should now return the correct state on acceptance to ensure the client doesn't block indefinitely waiting for its sync send to complete.

--
Tim Bish
Sr Software Engineer | RedHat Inc.
[email protected] | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

Reply via email to