You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/07/25 14:22:51 UTC
[jira] Commented: (CAMEL-2740) Using static queue as a reply queue
in InOut pattern causes memory leak
[ https://issues.apache.org/activemq/browse/CAMEL-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60895#action_60895 ]
Claus Ibsen commented on CAMEL-2740:
------------------------------------
See this FAQ about the correct way of using templates
http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html
And also try Camel 2.5 because the request-reply logic over JMS have been refactored a bit to cater for async routing engine.
> Using static queue as a reply queue in InOut pattern causes memory leak
> -----------------------------------------------------------------------
>
> Key: CAMEL-2740
> URL: https://issues.apache.org/activemq/browse/CAMEL-2740
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.2.0
> Environment: Windows 2003 server
> 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.
-
You can reply to this email to add a comment to the issue online.