Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com
 designates 209.85.223.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1355150640969-4660437.post@n4.nabble.com>
References: <1355150640969-4660437.post@n4.nabble.com>
Date: Mon, 10 Dec 2012 11:36:45 -0700
Message-ID: 
 <CAKS7T5OhWu7hV5-U5Mxhn0M_KGeMBtBqsasviEPet5D95B_X1A@mail.gmail.com>
Subject: Re: Broker Leak
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=20cf303f64eae60b3b04d083d8ac

--20cf303f64eae60b3b04d083d8ac
Content-Type: text/plain; charset=ISO-8859-1

That could be the case. When a temp dest goes away, it's subs do not
automatically go away. This is something we've been discussing recently.
Can you post the configs you used in your test, or better yet a unit test
that shows this?


On Mon, Dec 10, 2012 at 7:44 AM, Jerry Cwiklik <cwiklik@us.ibm.com> wrote:

> I am running AMQ broker v.5.6 on linux with 10G Xmx, 5G limit memoryUsage,
> producerFlowControl=false, no persistence, vmCursor and AUTO_ACKNOWLEDGE.
> There are a hundreds of producers and consumers, a few queues and a couple
> of hundred of temp queues. While watching broker memory in jConsole I
> notice
> a steady raise in OldGen. Forcing GC doesnt change anything. The broker
> eventually OOMs after a few days. The HeapAnalyzer shows 96% of heap in
> VmPendingMessageCursor. There are many messages destined for temp queues in
> this cursor.
>
> I created a simple test program where a Producer keeps sending messages to
> a
> Consumer which immediately sends a reply back to the Producer's temp queue.
> I kill the Producer with  -9, force GC on the broker and dump the heap.
> Looking at the heap, I can see that the VMPendingCursor holds messages for
> the temp queue which no longer exist! It looks to me that the broker never
> cleans up messages destined for temp queues which no longer exist leading
> to
> a memory leak. Attached is a snapshot from the heapAnalyzer showing a
> message in VMPendingMessageCursor.
>
> Is there a way to configure the broker to remove such messages? We
> currently
> dont expire messages (TTL=0). The broker knows when a temp queue is deleted
> so it should try to clean up messages associated with it.
>
> <http://activemq.2283324.n4.nabble.com/file/n4660437/heap-dump-leak.png>
>
> Regards, Jerry C
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Broker-Leak-tp4660437.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

--20cf303f64eae60b3b04d083d8ac--