Configure the thread pool on jetty and then you do not need that extra threads in the Camel route. Then you leverage the existing thread pools from jetty. That is the better way.
You can configure thread pool size of jetty on the component level http://camel.apache.org/jetty On Mon, Nov 23, 2015 at 3:18 PM, tomaswahlgren <[email protected]> wrote: > I can't get more than 64 simultaneous calls per endpoint, regardless of what > I set the threads value to. Is there another parameter, or is 64 a hard > limit? > > It keeps working when I use more clients, but I cant use more parallell > calls, i.e. a client have to wait until there is a free thread. > > My RouteBuilder: > > /public void configure() { > ... > > from("jetty:http://0.0.0.0:7076...";).routeId(MDP_ROUTE).threads(150, 150, > "mdpEndpointThread").loadBalance(router).to(<URL1><URL2>); > }/ > > Camel version 2.16 > Consumer: > jetty:http:0.0.0.0:7076/mdr/api/ifmdr?matchOnUriPrefix=true&enableMultipa‌rtFilter=false > Producer: > jetty:http:localhost:6080/say/hello1?bridgeEndpoint=true&throwExceptionOn‌Failure=false&disableStreamCache=true > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Settings-for-threads-per-endpoint-tp5774319.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
