Hi Not really. The template is at the end using the same code as the route builders does.
What versions of the products are you using? Can you provide a small sample application that has this flaw? Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: jayson.minard [mailto:[EMAIL PROTECTED] Sent: 17. september 2008 18:46 To: [email protected] Subject: ProducerTemplate and ActiveMQ component seems to leak threads With a route such as: from("activemq:queue:test.input").process(new TestProcessor("activemq:queue:test.output")); And in the TestProcessor class, if we do something like: // outEndPoint is derived from the constructor parameter and is "activemq:queue:test.output.something" Message msg = exchange.getIn(); ProducerTemplate producer = exchange.getContext().createProducerTemplate(); producer.sendBodyAndHeaders(outEndPoint, msg.getBody(), msg.getHeaders()); It leaks threads and holds open ActiveMQ sessions endlessly. We have the ActiveMQ component configured and pooling is on, and all other routes do not leak threads other than when we use ProducerTemplate. Is there something different needing to be done to make sure the pooling in ActiveMQ component is used when ProducerTemplate is the source of messages? Thanks for any help or advice... -- Jayson -- View this message in context: http://www.nabble.com/ProducerTemplate-and-ActiveMQ-component-seems-to-leak-threads-tp19536417s22882p19536417.html Sent from the Camel - Users mailing list archive at Nabble.com.
