Alternatively, if the failover transports retry logic is not adequate, it may
be worth considering to move that logic up into the application.
The failover transport is awesome, but it cannot foresee every possible
application concern.
Adding reconnects and recovery at the application level is no
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
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 mad
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
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.
On 01/22/2015 10:04 AM, nelsoncc wrote:
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/maxReconn
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.ht
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=false&useExponentialBackOff=false&initialReconnectDelay
