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? failover:(tcp://localhost:9995,tcp://localhost:9996)?timeout=3000&startupMaxReconnectAttempts=100&maxReconnectAttempts=100 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: http://activemq.2283324.n4.nabble.com/broker-config-if-destination-may-be-down-tp3086163p3089338.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
