This does help, thanks! But doesn't explain why would we get this behavior while pushing over a large number of messages (example - 500). The connection is lost and the EOFException is logged. A couple of questions:
1. Does the keepAlive flag need to be on the TransportConnector for ServerA, or part of the ActiveMQConnectionFactory URI, or both? 2. What about the EOFException. The way I understand it is the exception is happening because the TCPBufferedInputStream is returning a bad value for the first 4 bytes (aka - command) before the message has been completely sent over. We did do a TCP dump and did not see any missing packets or wholes in the packet transmissions. Could the Inactivity Monitor not be picking up the fact that information is being sent across the wire, the keep-alives are being dropped, and the Inactivity not seeing keep-alives is disconnecting the Bridge while messages are being transmitted? -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-to-JMS-Bridge-Connection-tp4684129p4684150.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
