A component is a singleton by default, and usually only created once and registered in the component cache in camel context.
Do your custom component not extend default component etc. On Wed, Aug 20, 2014 at 5:02 PM, martin11 <mato.kraj...@gmail.com> wrote: > I have a two threads (routes with different timer id in consumer). > I created my own camel component (with endpoint and producer). > This component should handle concurrency access (read/write) to datastore > (LDAP) for all threads. > > From debug I see that each thread/route create its own instance of component > (and of course it cache if singleton) but how can I have singleton of > myComponent for all threads/routes to handle concurrency from different > threads/routes? > > Thanks for any advice. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Component-singleton-for-all-routes-tp5755446.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/