Hi Tim Thanks
I now see that my client should be setting *jms.forceSyncSend=true* (although the ActiveMQ documentation has it as *jms.alwaysSyncSend=true*, so I am setting both) option in the connection URI. However, it is still operating asynchronously. I forgot to mention that I am using a failover URI (with just a single broker URI inside it) in order to make the client automatically retry a dropped connection. Could failover be forcing things into asynchronous mode? And/or should the syncSend parameters be tacked onto the outer URI vs. the inner URI ? In other words, is it: failover:( broker-uri-here?broker.params )?failover.params&sync.params OR failover:( broker-uri-here?broker.params&sync.params )?failover.params Thanks again in advance -- View this message in context: http://qpid.2158936.n2.nabble.com/synchronous-sending-using-javax-jms-MessageProducer-send-tp7660152p7660155.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
