This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Why does Camel use too many threads with ProducerTemplate
Skip to end of metadata
Go to start of metadata

Why does Camel use too many threads with ProducerTemplate?

A common reason is creating a new ProducerTemplate inside a Processor or bean method invocation.

You are not meant to create a ProducerTemplate for each message invocation; you are meant to create a single instance on startup and keep it around.

Also when you have finished using the ProducerTemplate you should call the stop() method to close down all the resources it has been using.

Its better to either explicitly create one on startup or get your IoC container (Spring or Guice) to inject it into your Processor or bean then it can take care of creating it and destroying all the resources when you have finished with it.

For instance using Spring you can define a template and have Spring handle the lifecycle of it:

    <camelContext xmlns="">
        <template id="template"/>

Then you can refer to the ProducerTemplate with the id template

  • No labels