Thanks for the pointers.
If I have a route of the form
from("direct:setStatusToReadyToShip").to("bean:orderHelper?method=setStatusToReadyToShip")
Then the route from from(...).to(...) will be effected by
defaultThreadProfile?
On Jul 3, 2016 3:39 PM, "Claus Ibsen" <[email protected]> wrote:
> Hi
>
>
> No Jetty has its own thread pooling, and you need to configure it
> using options on the jetty component
> http://camel.apache.org/jetty
>
> The thread pools in Camel is when you configure an explicit thread
> pool on a component that is of ExecutorService type. And also for all
> the EIPs that has thread pools.
>
>
> You can find some details at
> http://camel.apache.org/threading-model.html
>
> And I suggest if you want deeper knowledge then pickup a copy of the
> Camel in Action book.
>
> On Sun, Jul 3, 2016 at 12:06 PM, Debraj Manna <[email protected]>
> wrote:
> > Can some please explain me how does threadPool works in camel?
> >
> > Let's say I have a default threadPool defined in camelContext:-
> >
> > <threadPoolProfile id="defaultThreadPoolProfile"
> >
> > defaultProfile="true" poolSize="50" maxPoolSize="500" maxQueueSize="5000"
> >
> > rejectedPolicy="CallerRuns" />
> >
> > Also let's say I have some routes defined as below:-
> >
> > from("jetty:http://localhost:8888/orchestratorservice
> ").process(processor);
> >
> >
> from("direct:setStatusToReadyToShip").to("bean:orderHelper?method=setStatusToReadyToShip")
> >
> > Will the threads in jetty be limited by the size of
> > defaultThreadPoolProfile?
> >
> > Also let's say I create one more threadPool of size greater than the pool
> > size of defaultThreadPoolProfile in the orderBeans, how will this
> > threadPool behave?
> >
> > If I don't define any defaultThreadPool in camelContext what default
> values
> > it take?
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
