.nabble.com/maxReconnectAttempts-parameter-tp4690272p4690564.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
/maxReconnectAttempts-parameter-tp4690272p4690281.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
maxReconnectAttempts=1
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
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
Hi,
I'm trying to use the maxReconnectAttempts parameter, but without success.
I'm using a client connection with the following URI:
failover:(tcp://localhost:61616,tcp://localhost:61626)?randomize=falseuseExponentialBackOff=falseinitialReconnectDelay=1000startupMaxReconnectAttempts
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
Tks for your quick feedback. So what configuration should I use in the client
so it tries to reconnect always once, even if the broker is down?
Kind Regards,
Nelson Cintra
--
View this message in context:
http://activemq.2283324.n4.nabble.com/maxReconnectAttempts-parameter-tp4690272p4690281
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
On 01/22/2015 09:35 AM, nelsoncc wrote:
Hi,
I'm trying to use the maxReconnectAttempts parameter, but without success.
I'm using a client connection with the following URI:
failover:(tcp://localhost:61616,tcp://localhost:61626)?randomize=falseuseExponentialBackOff=falseinitialReconnectDelay
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.