camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thestubborncamel <>
Subject Re: Threading Model in Camel
Date Sat, 21 Jan 2012 22:11:55 GMT
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]" <>

> 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
> 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]
> [2]
> Babak 
> If you reply to this email, your message will be added to the discussion below:
> To unsubscribe from Threading Model in Camel, click here.

View this message in context:
Sent from the Camel - Users mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message