Yes, Camel will share your Processors, Beans etc. They should be thread safe.
Best, Christian Sent from a mobile device Am 22.08.2012 22:20 schrieb "javakurious" <[email protected]>: > Thanks for the response. Please bear with me as I am new to using Camel and > also trying to understand concurrency in this environment. > > I am thinking how it would be if the web service were deployed as stateless > EJB beans. Here is my understanding: > > Glassfish creates a pool of these stateless beans(say a pool of 5). And if > there are 5 HTTP thread workers (web container in glassfish) invoking > webservice, each HTTP thread will be invoking a different instance on a EJB > bean and that bean is dedicated to that thread for the duration of that > method call. So, a thread will not be waiting on other threads to 'free up' > an instance of the Bean. > > In camel environment, does different HTTP thread access the same instance > of > processor/bean ? If a processor has a synchronized method, do other threads > wait for synchronized blocks to complete or access a different instance of > that bean. > > Thanks > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/concurrent-users-with-camel-routes-tp5717888p5717898.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
