activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From logosdev <>
Subject Re: broker config if destination may be down
Date Wed, 15 Dec 2010 16:20:58 GMT

Setting the timeout on the failover transport does indeed cause that initial
connection to abort, which allows the broker to start up and enqueue bridged
messages.  This is what I wanted.

However, I don't see any indication that the failover transport ever tries
again.  Using a url like the following, should I expect the transport to
automatically reconnect at some point after the timeout exception is thrown?


Or do all these parameters like startupMaxReconnectAttempts and
initialReconnectDelay only work if there is no timeout?

Is this a case where I have to add a transport listener to listen for the
timeout and schedule a reconnect attempt?

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message