We are using a single template for the whole application. We don't create new ones and are still seeing this behavior from one part of our application. We are digging deeper now to try and create a more concise case that we can test with.
Thanks for your help, Joe This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system. You may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet. -----Original Message----- From: Claus Ibsen [mailto:[email protected]] Sent: Tuesday, December 28, 2010 1:41 AM To: [email protected] Cc: David Cannon Subject: Re: Thread creation leak problem 2.0M3 Read this FAQ http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html On Tue, Dec 28, 2010 at 2:59 AM, Joe White <[email protected]> wrote: > We are using camel 2.0M3 in tomcat 5 and are having a problem where over > time more and more threads are created and never reclaimed. The threads > are labeled "Camel thread X: ActiveMQComponent" where X is an ever > increasing number. Each thread is "waited" repeatedly over time but > never complete. Eventually this leads to resource contention in the > application. > > > > - In the application we only publish messages to queues using > the InOut pattern. The code is below. > > - We use the same producer template for all of the publishing. > The spring definition of the template is below. > > > > Anybody have a resolution or a recommendation on how to troubleshoot the > issue? > > > > We are using: > > - activemq-core-5.3.2.jar > > - activemq-camel-5.3.2.jar > > - camel-core-2.0-M3.jar > > - camel-spring-2.0-M3.jar > > - spring-core-2.5.5.jar > > > > Publish code: > > Map<String, DalMap> result = (Map<String, > DalMap>)camelTemplate.sendBody("jms:queue:" + serviceName > +"?requestTimeout=" + timeout+"&jmsMessageType=Object", > ExchangePattern.InOut, message); > > > > Template Definition: > > <camel:camelContext id="camel"> > > <!-- Enable JMX connector so we can connect to the server and browse > mbeans --> > > <camel:jmxAgent id="agent" createConnector="false" > registryPort="1099" serviceUrlPath="/jmxrmi" /> > > <camel:template id="camelTemplate"/> > > </camel:camelContext> > > > > Thank you for your help > > Joe > > > > This message is confidential. It may also be privileged or otherwise > protected by work product immunity or other legal rules. If you have > received it by mistake, please let us know by e-mail reply and delete it > from your system. You may not copy this message or disclose its contents > to anyone. The integrity and security of this message cannot be > guaranteed on the Internet. > > > > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
