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/15 14:47:24 UTC
[jira] Created: (AMQ-3038) Possible Memory-Leak as
ActiveMQTempDestinations don't get deleted when ActiveMQConnection.close()
is called
Possible Memory-Leak as ActiveMQTempDestinations don't get deleted when ActiveMQConnection.close() is called
------------------------------------------------------------------------------------------------------------
Key: AMQ-3038
URL: https://issues.apache.org/activemq/browse/AMQ-3038
Project: ActiveMQ
Issue Type: Bug
Environment: trunk
Reporter: Norman Maurer
As TemporaryQueue and TemporaryTopic is bound to the scope of a Connection both should be deleted when the Connection is closed. If that's not done its possible to see a Memory-Leak on heavy usage really soon
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-3038) Possible Memory-Leak as
ActiveMQTempDestinations don't get deleted when ActiveMQConnection.close()
is called
Posted by "Norman Maurer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer updated AMQ-3038:
-------------------------------
Attachment: AMQ-3038.diff
This should fix it..
> Possible Memory-Leak as ActiveMQTempDestinations don't get deleted when ActiveMQConnection.close() is called
> ------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3038
> URL: https://issues.apache.org/activemq/browse/AMQ-3038
> Project: ActiveMQ
> Issue Type: Bug
> Environment: trunk
> Reporter: Norman Maurer
> Attachments: AMQ-3038.diff
>
>
> As TemporaryQueue and TemporaryTopic is bound to the scope of a Connection both should be deleted when the Connection is closed. If that's not done its possible to see a Memory-Leak on heavy usage really soon
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.