On 01/22/2015 10:14 AM, nelsoncc wrote:
That parameter is what I'm using, but it ignores the parameter and never
reconnects again.
Kind Regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/maxReconnectAttempts-parameter-tp4690272p4690283.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The failover transport does its reconnect work in a background thread so
it did try once and gave up it's just that it happens so fast that you
hadn't restarted the broker yet. In general a maxReconnectAttempts
value of one only makes sense in the case where you want to select from
a list of two brokers in the failover URI and then stop (randomize
should be off).
To be clear, the reconnect attempts do not take place on the send call,
they are async.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
