You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Markus Wolf (JIRA)" <ji...@apache.org> on 2009/02/23 11:26:59 UTC
[jira] Created: (AMQ-2138) Memory Leak in ActiveMQConnection
Memory Leak in ActiveMQConnection
---------------------------------
Key: AMQ-2138
URL: https://issues.apache.org/activemq/browse/AMQ-2138
Project: ActiveMQ
Issue Type: Bug
Components: Connector
Environment: Tomcat 6 + ActiveMQ 5.1
Reporter: Markus Wolf
We discovered a memory leak in the ActiveMQConnection class.
In our setup we have an activemq 5.1 embedded in our webapplication. On undeployemnt (more specially on connection close) the ThreadPoolExecutor is kept in memory and could not be garbage collected, because of the ThreadFactory which is loaded by our webapp classloader. A reference to it is held by the ThreadPoolExecutor.
This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2138) Memory Leak in ActiveMQConnection
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated AMQ-2138:
------------------------------
Fix Version/s: 5.5.0
(was: 5.4.1)
> Memory Leak in ActiveMQConnection
> ---------------------------------
>
> Key: AMQ-2138
> URL: https://issues.apache.org/activemq/browse/AMQ-2138
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Tomcat 6 + ActiveMQ 5.1
> Reporter: Markus Wolf
> Fix For: 5.5.0
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We discovered a memory leak in the ActiveMQConnection class.
> In our setup we have an activemq 5.1 embedded in our webapplication. On undeployemnt (more specially on connection close) the ThreadPoolExecutor is kept in memory and could not be garbage collected, because of the ThreadFactory which is loaded by our webapp classloader. A reference to it is held by the ThreadPoolExecutor.
> This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2138) Memory Leak in ActiveMQConnection
Posted by "Markus Wolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Wolf updated AMQ-2138:
-----------------------------
This is also the case for the ASYNC_TASKS ThreadPoolExecutor in the InactivityMonitor class.
> Memory Leak in ActiveMQConnection
> ---------------------------------
>
> Key: AMQ-2138
> URL: https://issues.apache.org/activemq/browse/AMQ-2138
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Tomcat 6 + ActiveMQ 5.1
> Reporter: Markus Wolf
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We discovered a memory leak in the ActiveMQConnection class.
> In our setup we have an activemq 5.1 embedded in our webapplication. On undeployemnt (more specially on connection close) the ThreadPoolExecutor is kept in memory and could not be garbage collected, because of the ThreadFactory which is loaded by our webapp classloader. A reference to it is held by the ThreadPoolExecutor.
> This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2138) Memory Leak in ActiveMQConnection
Posted by "Markus Wolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Wolf updated AMQ-2138:
-----------------------------
And there are at least two more of this cases:
* In TcpTransport the field SOCKET_CLOSE
* In TaskRunnerFactory the field executor
> Memory Leak in ActiveMQConnection
> ---------------------------------
>
> Key: AMQ-2138
> URL: https://issues.apache.org/activemq/browse/AMQ-2138
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Tomcat 6 + ActiveMQ 5.1
> Reporter: Markus Wolf
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We discovered a memory leak in the ActiveMQConnection class.
> In our setup we have an activemq 5.1 embedded in our webapplication. On undeployemnt (more specially on connection close) the ThreadPoolExecutor is kept in memory and could not be garbage collected, because of the ThreadFactory which is loaded by our webapp classloader. A reference to it is held by the ThreadPoolExecutor.
> This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2138) Memory Leak in ActiveMQConnection
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-2138:
----------------------------
Fix Version/s: 5.4.0
> Memory Leak in ActiveMQConnection
> ---------------------------------
>
> Key: AMQ-2138
> URL: https://issues.apache.org/activemq/browse/AMQ-2138
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Tomcat 6 + ActiveMQ 5.1
> Reporter: Markus Wolf
> Fix For: 5.4.0
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We discovered a memory leak in the ActiveMQConnection class.
> In our setup we have an activemq 5.1 embedded in our webapplication. On undeployemnt (more specially on connection close) the ThreadPoolExecutor is kept in memory and could not be garbage collected, because of the ThreadFactory which is loaded by our webapp classloader. A reference to it is held by the ThreadPoolExecutor.
> This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2138) Memory Leak in ActiveMQConnection
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated AMQ-2138:
---------------------------------
Fix Version/s: 5.4.1
(was: 5.4.0)
> Memory Leak in ActiveMQConnection
> ---------------------------------
>
> Key: AMQ-2138
> URL: https://issues.apache.org/activemq/browse/AMQ-2138
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Tomcat 6 + ActiveMQ 5.1
> Reporter: Markus Wolf
> Fix For: 5.4.1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We discovered a memory leak in the ActiveMQConnection class.
> In our setup we have an activemq 5.1 embedded in our webapplication. On undeployemnt (more specially on connection close) the ThreadPoolExecutor is kept in memory and could not be garbage collected, because of the ThreadFactory which is loaded by our webapp classloader. A reference to it is held by the ThreadPoolExecutor.
> This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.