You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2011/01/20 17:13:44 UTC
[jira] Resolved: (AMQ-3038) Possible Memory-Leak as
ActiveMQTempDestinations don't get deleted when ActiveMQConnection.close()
is called
[ https://issues.apache.org/jira/browse/AMQ-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-3038.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.5.0
Patch applied with svn revision 1061365. Thanks!
> Possible Memory-Leak as ActiveMQTempDestinations don't get deleted when ActiveMQConnection.close() is called
> ------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3038
> URL: https://issues.apache.org/jira/browse/AMQ-3038
> Project: ActiveMQ
> Issue Type: Bug
> Environment: trunk
> Reporter: Norman Maurer
> Assignee: Dejan Bosanac
> Fix For: 5.5.0
>
> 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.