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.
