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 not that complicated, if the code is structured well to support it and the recovery paths are clearly defined. So, the failover transport options are not the only possible solution, but perhaps the easiest/shortest path to victory. -- View this message in context: http://activemq.2283324.n4.nabble.com/maxReconnectAttempts-parameter-tp4690272p4690564.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
