You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Norman Maurer (JIRA)" <ji...@apache.org> on 2010/11/16 10:03:24 UTC
[jira] Created: (AMQ-3041) TemporyQueue will never get unregisterd
from JMX which leads to a memory leak
TemporyQueue will never get unregisterd from JMX which leads to a memory leak
-----------------------------------------------------------------------------
Key: AMQ-3041
URL: https://issues.apache.org/activemq/browse/AMQ-3041
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.4.1
Environment: activemq 5.4.1 and 5.5-SNAPSHOT
Reporter: Norman Maurer
Fix For: 5.5.0
When you use Session.createTemporaryQueue(...) you will see that the TemporaryQueue will get added to JMX. Now when you call TemporaryQueue.delete() it will not get delete from JMX. So when you make heavy use of TemporaryQueues you will see that the entries in JMX will get bigger and bigger as they will never get removed on delete. This can lead to an OOM very frequently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-3041) TemporyQueue will never get unregisterd
from JMX which leads to a memory leak
Posted by "Norman Maurer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer updated AMQ-3041:
-------------------------------
Affects Version/s: 5.5.0
> TemporyQueue will never get unregisterd from JMX which leads to a memory leak
> -----------------------------------------------------------------------------
>
> Key: AMQ-3041
> URL: https://issues.apache.org/activemq/browse/AMQ-3041
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.1, 5.5.0
> Environment: activemq 5.4.1 and 5.5-SNAPSHOT
> Reporter: Norman Maurer
> Fix For: 5.5.0
>
>
> When you use Session.createTemporaryQueue(...) you will see that the TemporaryQueue will get added to JMX. Now when you call TemporaryQueue.delete() it will not get delete from JMX. So when you make heavy use of TemporaryQueues you will see that the entries in JMX will get bigger and bigger as they will never get removed on delete. This can lead to an OOM very frequently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-3041) TemporyQueue will never get
unregisterd from JMX which leads to a memory leak
Posted by "Norman Maurer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63370#action_63370 ]
Norman Maurer commented on AMQ-3041:
------------------------------------
After some debugging I see that when the temprary queue is created it call:
ManagedTempQueueRegion.createDestination(....)
But when call TemporaryQueue.delete() it never call;:
ManagedTempQueueRegion.removeDestination(....)
I still try to understand why
> TemporyQueue will never get unregisterd from JMX which leads to a memory leak
> -----------------------------------------------------------------------------
>
> Key: AMQ-3041
> URL: https://issues.apache.org/activemq/browse/AMQ-3041
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.1, 5.5.0
> Environment: activemq 5.4.1 and 5.5-SNAPSHOT
> Reporter: Norman Maurer
> Fix For: 5.5.0
>
>
> When you use Session.createTemporaryQueue(...) you will see that the TemporaryQueue will get added to JMX. Now when you call TemporaryQueue.delete() it will not get delete from JMX. So when you make heavy use of TemporaryQueues you will see that the entries in JMX will get bigger and bigger as they will never get removed on delete. This can lead to an OOM very frequently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.