camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-2740) Using static queue as a reply queue in InOut pattern causes memory leak
Date Wed, 09 Nov 2011 17:29:51 GMT


Claus Ibsen commented on CAMEL-2740:

Well the sample project from David itself also causes high memory occupation as it creates
1.000.000 tasks on the executor service pool, which is stored in memory. For example using
a sample with for example 50.000 tasks does not take up so much memory.

> Using static queue as a reply queue in InOut pattern causes memory leak
> -----------------------------------------------------------------------
>                 Key: CAMEL-2740
>                 URL:
>             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
>            Assignee: Claus Ibsen
>             Fix For: 2.7.5, 2.8.3, 2.9.0
>         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:!default.jspa
For more information on JIRA, see:


View raw message