activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: Broker Leak
Date Tue, 11 Dec 2012 19:16:05 GMT
No, it's not related to the half-closed socket. Everything gets cleaned up
properly on that end.

The destination (TempQueue) is removed from the broker as expected, but the
producer connection (on the broker side) from the SprignConsumerWithReply
module has an object (ProducerExchange) that keeps a reference to the
TempQueue because that's where it last sent a message.

The reference unfortunately keeps the entire object representing the
TempQueue around, including the references it has to the queue cursor. If
the producer sends another message, then that reference gets updated to
wherever the new message is being sent.

This is just cleanup that happens within the broker. The destination is no
longer considered there when it's in this state. The messages are not
reachable for dispatching or consuming.

On Tue, Dec 11, 2012 at 11:42 AM, Jerry Cwiklik <> wrote:

> Thanks, yes this is true that there is an open connection to a temp queue
> from the the SpringConsumerWithReply service. This is probably a common
> scenario where one deploys a service process which services requests from
> clients which can disappear at any time. Cleaning up unused/dead
> connections
> would be an application concern. No argument there.
> What I dont understand is why do I have messages in the broker destined for
> a temp queue which no longer exist. When I kill the ProducerWithConsumer,
> the temp queue is removed but the broker retains messages for it, which
> causes a leak. Is this releated to what Gary mentioned, namely half closed
> socket? We do use soWriteTimeout but not soTimeout. I will try to run the
> test case with that.
> -Jerry C
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

*Christian Posta*
twitter: @christianposta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message