There are 3 scenarios where ActiveMQ behaved as designed: 1. Outbound Bridge disabled. This always worked. 2. With Outbound Bridge enabled, it intermittently worked for specific embedded brokers and not for others, then it would flip on us. Same configs an all. 3. With Outbound Bridge enabled, we moved Broker A to a new server that is 1 network hop to Broker B. Instead of 2 network hops. This has worked for the past few days.
In wanting to do some more testing on the TCP Dump, we moved Broker A back to its original Server which is 2 network hops to Broker B, and the problem is not showing up. Like I mentioned before, it is a hard problem to reproduce. It will work for awhile, and then all of a sudden it will stop working. But once it does happen, it keeps happening until some random time that it starts working. I know this is sounding crazy. But there is no rhyme or reason for ActiveMQ to stop working. It just does, and we do not understand it. Could it be a race condition? Maybe. Could someone be doing something to the network and we are unaware of it? Maybe. Could be a number of reasons. Currently, we are monitoring the Brokers and waiting to see if it happens again. If/when it happens again, we will get some more TCP Dump info, turn on TRACE logging not only at the application level, but also on the TCPTransport. Basically, try to get as much info as we can. I will post back to this forum when we do. -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-to-JMS-Bridge-Connection-tp4684129p4684283.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
