Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Tue, 14 Feb 2012 07:13:34 -0800 (PST)
From: john <john.fansler@ateb.com>
To: users@activemq.apache.org
Message-ID: <1329232414163-4387316.post@n4.nabble.com>
Subject: ACtiveMQConnection leak
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm running the fuse 4.4.1-fuse-01-13 ESB release which includes camel 2.8
and activemq 5.5.1.

I have a simple camel route whose job is to ensure that a message queue has
X number of records from a db queued up for a consumer. When the timer on
the route fires, a POJO is called. 

The bean uses the camel producer template to send a message to
activemq:queue:ActiveMQ.Statistics.Destination.MYQUEUE to determine how many
messages are currently on the queue. I have the statistics plugin enabled.

The issue I have is that when this route is enabled, I see a slow climb in
PS Old Gen memory. A heap dump shows a ton of ActiveMQConnection and
TransportConnectState objects.

This didn't occur in the much older fuse release we were using. It used
camel 2.2 and activemq 5.4.0.

I do have activemq pooling enabled in the spring configuration. I can
include that information if needed.

I appreciate any help!

-john

--
View this message in context: http://activemq.2283324.n4.nabble.com/ACtiveMQConnection-leak-tp4387316p4387316.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.