The configuration is properly using the failover transport, and the logs show reconnects. So, the TCP transport exception-handling is not the problem.
Does the EOF exception occur every time after the problem starts? The stack trace suggests a problem at the level of the OpenWire protocol. Perhaps there is a bug caused by specific messages. One way to tell would be to drain messages after the problem occurs and see if that helps at all (assuming remaining messages do not exhibit the same problem). Are all the brokers running 5.10.0? -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-to-JMS-Bridge-Connection-tp4684129p4684130.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
