[
https://issues.apache.org/jira/browse/AMQ-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2991.
-----------------------------
Resolution: Not A Problem
Working as designed. A temp destination exists for the life of the Connection.
The test case create a single connection for the requestor and the responder
so each request / response cycle creates a new destination that will live on
after the cycle. You could just use one temp destination for this pattern.
You could also look into auto removing inactive destinations for this:
http://activemq.apache.org/delete-inactive-destinations.html
> ActiveMQ leaks memory for a typical request/response pattern (temporary
> queues)
> -------------------------------------------------------------------------------
>
> Key: AMQ-2991
> URL: https://issues.apache.org/jira/browse/AMQ-2991
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.1
> Environment: Windows 7, JRE 1.6
> Reporter: Manuel Teira
> Priority: Critical
> Attachments: AMQ2991.java
>
>
> Usage of temporary queues to implement a request/response pattern seems to
> lead to memory leakages in the activemq broker. This leakage looks related
> with the creation of temporary queues in the broker.
> I'm attaching a test case were enabling or disabling temporary queues usage,
> makes a difference in the amount of committed heap memory requested by the
> VM: Using temporary queues makes heap memory to increment with time, whereas
> disabling it makes the test runs with constant memory numbers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
