You might be hitting bug AMQ-3277. There is a patch attached to that bug report which creates a new transport to solve the problem.
https://issues.apache.org/jira/browse/AMQ-3277 Note that AMQ-3277 has not been validated against 5.5.0 yet. -- View this message in context: http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-3213-failover-doesn-t-reconnect-after-broker-restart-tp3343914p3545448.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
