[
https://issues.apache.org/jira/browse/CAMEL-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146651#comment-13146651
]
David Valeri commented on CAMEL-2740:
-------------------------------------
Also, the attached test uses 2.9-RC1. The steady slowdown with a temporary
reply destination was due to Eclipse's console window slowing down the logging
activities when running the test in Eclipse. Once Eclipse was out of the mix,
using a temporary reply destination performed flawlessly in a 30 minute test
run.
> 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
> Attachments: CAMEL-2740 Memory Usage.jpg, CAMEL-2740.tar.gz
>
>
> 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
