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
  • ServicePool

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


Camel supports pluggable pools for services. At this time of write we have pools for:

  • Producer

The default producer service pool is org.apache.camel.impl.DefaultProducerServicePool and is used by default in Camel for pooling Producer.

The need for pooling Producer is only apparent in some Components in Camel to support thread safe producers and support concurrency. And using pooling we can improve performance as we do not have the overhead of creating, starting and stopping the Producer at each invocation. So where is it needed then? Well these components uses pooled producers:


By default Camel uses a shared org.apache.camel.impl.DefaultProducerServicePool provided by CamelContext. This default pool will pool up till 100 producers per Endpoint. So if you have 6 endpoints there can be up till 6 x 100 in total in the pool, where each distinct Endpoint have a limit of up till 100 producers.


The producer service pool identify a producer as being pool capable if the producer implements the marker interface org.apache.camel.SerivcePoolAware.
As the producer will be pooled and thus long lived, your producer should be able to automatic safely recover lost connection. Usually you implement logic that re connects if needed.

See Also