Hi Justin, Cory Adams [1] discovered a bug in the JMS AMQP 1.0 client handling of a System Property which prevents JVM wide setting of the synchronous publish behaviour. While there is a workaround (to set it on the connection URL for each connection), the fix [2] is isolated to this client and low impact and low risk. If possible I'd like to get this into 0.30
-- Rob [1] http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-client-in-production-tp7611393p7612664.html [2] JIRA: https://issues.apache.org/jira/browse/QPID-6050
