activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (AMQ-3997) Memory leak in activemq-pool
Date Tue, 28 Aug 2012 11:06:07 GMT


Claus Ibsen commented on AMQ-3997:

This is the AMQ pooled configuration I am using in that test from the link above, the code
from the github project

	<bean id="connectionFactory" class="org.apache.activemq.pool.PooledConnectionFactory"
init-method="start" destroy-method="stop">
		<property name="maxConnections" value="1" />
		<property name="maximumActive" value="10"/>
		<property name="connectionFactory">
			<bean class="org.apache.activemq.ActiveMQConnectionFactory">
				<property name="brokerURL" value="tcp://localhost:61616" />
> Memory leak in activemq-pool
> ----------------------------
>                 Key: AMQ-3997
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0
>            Reporter: Claus Ibsen
>             Fix For: 5.7.0
>         Attachments: bad.png
> The org.apache.activemq.pool.PooledConnectionFactory from activemq-pool has a severe
memory leak when using it for sending a lot of messages. Over time this causes memory to be
eaten up.
> I have tracked it down to the following tickets:
> - AMQ-3680, which keeps adding event listeners, despite previously added
> - AMQ-2643, code which keep track of loaned sessions, causing JVM to create too many
ConcurrentLinkedQueue$Node instances
> There may be others. But with resolutions to those I can get the pool to not eat memory,
and keep memory consumption low.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message