Thanks for a quick response. So, just to confirm - message processing is handled on the consumer thread of the transport (http jetty server) . i.e.,processing is not dispatched to any managed thread pool , right?
On Jan 21, 2012, at 1:29 PM, "Babak Vahdat [via Camel]" <[email protected]> wrote: > Hi, > > The Jetty consumer (HTTP-Server) of the camel-jetty component makes use of > the implementations of [1] to process the incoming HTTP request. > > Take a look at Component Options [2] for the possible customizations of > threadPool/minThreads/maxThreads etc. > > And you can both configure your own threadPool both in Java or Xml. As an > example in Xml you would do something like: > > <bean id="myThreadPool" > class="org.eclipse.jetty.util.thread.QueuedThreadPool"> > customize it the way you want to have it > </bean> > > <bean id="jetty" > class="org.apache.camel.component.jetty.JettyHttpComponent"> > <property name="threadPool" ref="myThreadPool"/> > </bean> > > And in case of Java you can wire exactly the same way as above through > "coding". However IMHO it's better/easier to wire the objects in Xml (Spring) > and code the Camel routes in Java DSL. However this is just a matter of > personal taste. > > [1] > http://download.eclipse.org/jetty/7.5.4.v20111024/apidocs/org/eclipse/jetty/util/thread/ThreadPool.html > [2] http://camel.apache.org/jetty > > Babak > > If you reply to this email, your message will be added to the discussion > below: > http://camel.465427.n5.nabble.com/Threading-Model-in-Camel-tp5163081p5163179.html > To unsubscribe from Threading Model in Camel, click here. > NAML -- View this message in context: http://camel.465427.n5.nabble.com/Threading-Model-in-Camel-tp5163081p5163396.html Sent from the Camel - Users mailing list archive at Nabble.com.
