activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin C." <>
Subject Re: AMQ does not drop connection on stomp client ungraceful shutdown
Date Sun, 03 Jul 2011 10:18:41 GMT

it sounds to me that it simply takes that long for the STOMP protocol
to realize that the connection died. Maybe you can enable
tcp.keepalive on the connection via the configuration URL?

You might also have a look at the keepalive options for your transport
connection, and if you are on Linux and cannot change the options, you
may want to look into which also
describes a LD_PRELOAD based approach to set TCP keepalive options for
sockets of foreign programs.

Best regards,

On Sat, Jul 2, 2011 at 1:10 AM, reachrichrulez <> wrote:
> we have an AMQ 5.3.2. running on server-1 and two perl stomp consumers on
> server-2 and server-3 consuming from the same queue. I have 10 messages that
> are being consumed (5 by each consumer)
> when I shutdown one consumer gracefully, the other consumer gets the
> messages instantly.
> Heres the issue -
> When I power off the on consumer box (case of a BCP event) the other
> consumer does not get the messages untill 8 to 10 minutes after. When I
> connected to the broker through jconsole. I still see the connection of the
> powered-off box. When I stopped the connection (stop() button) the other
> consumer started receiving the messages.
> Can someone help?
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

View raw message