On 01/22/2015 11:00 AM, nelsoncc wrote:
Hi,
If I use the URI:
failover:(tcp://localhost:61616,tcp://localhost:61626)?randomize=false
The thread blocks in sending message, and only unlocks when broker is
started.
Since I don't want to block the thread I can fix my problem using timeout
parameter.
I thought the reconnect attempt was made in sendMessage and not in
background thread, that's the reason I was trying to use the
maxReconnectAttempts parameter.
Can you confirm if the the timeout parameter is my only solution?
Kind Regards,
Nelson
--
View this message in context:
http://activemq.2283324.n4.nabble.com/maxReconnectAttempts-parameter-tp4690272p4690288.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Yes, you need to use timeout to cause send to return.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
