Hi

If you only need one time response, then stop the template after
usage. Otherwise it keeps resources "warn".

And see this FAQ too
http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html

On Mon, May 19, 2014 at 7:05 PM, elena <[email protected]> wrote:
> Hi,
>
> Our company use ActiveMQ 5.6.0 and Camel 2.10.0. We noticed that
> ProducerTemplate creates too much threads
> TemporaryQueueReplyManager[temporary]-1 and
> JmsReplyManagerTimeoutChecker[queueName] when sending requests. The threads
> have a waiting status. This causes a problem on our production system
> deployed on Linux PC. The system has dozens of queues and dozens of clients
> sending requests to get data. Is there a way to eliminate the number of
> these threads? Why they are not stopped when producer template received the
> response?
>
> Below is the excerpt from the stack trace:
>
> org.apache.camel.ProducerTemplate.requestBody(java.lang.String,
> java.lang.Object)
> com.sick.service.ObjectDataService.findSortListByTunnel(java.lang.String,
> java.lang.Integer)
> ......
>
> As recommended, we use only one camel template:
>
> <camel:camelContext id="ent-camel-client"
> xmlns="http://camel.apache.org/schema/spring";>
>         <camel:contextScan />
>         <camel:jmxAgent id="agent" createConnector="false" />
>         <camel:template id="camelTemplate" />
> </camel:camelContext>
>
> Thanks,
> Elena
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/ProducerTemplate-creates-too-much-threads-tp5751299.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: [email protected]
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Reply via email to