On 08/21/2012 11:42 AM, ShlomiJ wrote:
We noticed that *after an idle period* (around 40 minutes), during which no
new message is put in MyQueue, *when finally a message is sent* over the
queue, a *SocketException *is reported in the broker's log.
We were able to verify this by the second, from examining the producer log,
the broker log and the messages pending in the queue.
We suspect it now to be a firewall issue, actually (but without evidence at
the time).
Still, any thoughts will be appreciated.
SJ
--
View this message in context:
http://camel.465427.n5.nabble.com/Consumers-to-ActiveMQ-shotdown-but-not-reconnecting-even-when-failover-is-used-tp5717552p5717782.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You can try to add a keep alive to the TCP or SSL transport in ActiveMQ.
Most firewall problems I have had in various protocols like SSH have
been solved that way.
http://activemq.apache.org/tcp-transport-reference.html
--
Miguel Ruiz Velasco Sobrino
