camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ShlomiJ <>
Subject Consumers to ActiveMQ shotdown but not reconnecting, even when failover is used
Date Thu, 16 Aug 2012 14:28:43 GMT
hi there,

Having a machine running an ActiveMQ (5.5.1) broker.

Another machine runs our Camel (2.9.0) context.

The connection between the 2 is set exactly as described in *Using
connection pooling* in , with the following configuration:

*brokerUrl* =
*concurrentConsumers* = 200

In Camel context we define a thread pool with

The route is a simple 'from activemq' one:

&lt;from uri="activemq:queue:MyQueue" /&gt; &lt;!-- no more parameters here

&lt;threads executorServiceRef="poolRef" /&gt;
... etc.

*_After a while (1 to 2 days) the consumers are gone!_*

During the life-cycle of the application we see many successful
re-connections done by the failover ("/failover.FailoverTransport -
Connection established/").

The "keep alive" I'm familiar with (in order to not have so many
re-connections) is ActiveMQ's wireFormat configuration, but we could not
configure the broker connection with both failover and wireFormat

Then after a while, from some point on, it simply stops reconnecting.

We restart the route in order to make it reconnect again.

We might see "/Transport failed: Connection
reset/" in the ActiveMQ's log (I'm not sure that always).
This way or the other, we still expect the consumers to reconnect.

Why does the failover stop reconnecting?

Is there a better configuration to use?

What exactly is getting disconnected? Is it something in ActiveMQ or in

thanks for future help


View this message in context:
Sent from the Camel - Users mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message