You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "David Valeri (Updated) (JIRA)" <ji...@apache.org> on 2011/11/08 23:33:51 UTC
[jira] [Updated] (CAMEL-2740) Using static queue as a reply queue
in InOut pattern causes memory leak
[ https://issues.apache.org/jira/browse/CAMEL-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri updated CAMEL-2740:
--------------------------------
Environment: Originally reported on Windows 2003 server and recently confirmed on OSX in a stand alone unit test. (was: Windows 2003 server)
Fix Version/s: (was: 2.5.0)
> Using static queue as a reply queue in InOut pattern causes memory leak
> -----------------------------------------------------------------------
>
> Key: CAMEL-2740
> URL: https://issues.apache.org/jira/browse/CAMEL-2740
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.2.0
> Environment: Originally reported on Windows 2003 server and recently confirmed on OSX in a stand alone unit test.
> Reporter: Qingyi Gu
>
> I am running JBoss, ActiveMQ and Camel for my application. In the InOut pattern, I am using a predefined static queue as a reply queue. After running for a while, the memory usage of JBoss keeps growing and growing until it hits outOfMemory error and app server is totally hung. I monitor the thread in jconsole, I can see the jms connection/session keeps growing and growing.
> But once I switch to use temp queue for InOut pattern, this problem goes away.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira