camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gert Vanthienen <>
Subject Re: Camel + ActiveMQ in Tomcat6
Date Tue, 24 Feb 2009 14:21:59 GMT

Could you verify that it is not a thread leak that is causing the 
PermGen memory leak?  If you have threads being left behind when 
undeploying the WAR file (e.g. a JMS connection not closed properly), 
these threads will probably hang on to the classloader. 



James Strachan wrote:
> 2009/2/24 Markus Wolf <>:
>> Hash: SHA1
>>>> this approach does not help me, since when the ActiveMQ is created by
>>>> tomcats webapplication classloader it cannot be undeployed.
>>> You don't have to create the broker in the WAR (or you could put it in
>>> another WAR). This approach works totally fine if you are using the
>>> ActiveMQ JMS client with Camel.
>> But it requires to put the activemq-core dependency to the webapp for
>> creating the ConnectionFactory for ActiveMQ, doesn't it? Or am I missing
>> something here.
> Yes. How else could you use ActiveMQ from a web app?
>> Even starting the ConnectionFactory produce memory leaks in the webapp
>> classloader.
> Not sure what you mean by "memory leak in the web app class loader".
> Do you consider adding a class to a class loader a leak? :)

View raw message