On 03/07/2017 10:38 AM, Vince Cole wrote:
Thanks
I now see that my client should be setting *jms.alwaysSyncSend=true*
(although the qpid documentation has it as *jms.forceSyncSend=true*, so I am
setting both) option in the connection URI.
This is the ActiveMQ mailing list so my assumption is you are using the
ActiveMQ JMS client, if not you might want to clarify what it is you are
using.
However, it is still operating asynchronously.
How are you testing this?
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://activemq.2283324.n4.nabble.com/Synchronous-message-production-tp4723171p4723207.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
