Hi

We're using Camel 2.0 with Activemq 5.3.
Our app uses Camel jms remoting.
It's connecting to two discrete ActiveMQ brokers using the failover transport randomly. Everything works fine at first.

The problem happens when the app is idle for more than 30 seconds. After that any remote call will trigger Activemq client to reconnect and may end up connecting to another broker. But the problem is the Requestor does not reconnect and still connected to the original broker. The result is calls are sent to one broker but the Requestor is listening to a different broker for the response.

Is there a way to force the Requestor to use the same connection as the producers?

--Ming

Reply via email to