You likely need to configure the jetty server thread pool. That is the thread pool that matters the most as it has the worker threads that Camel uses when routing from jetty -> to jetty
On Tue, Nov 24, 2015 at 9:37 AM, tomaswahlgren <[email protected]> wrote: > Thanks for the prompt reply Claus, appriciate it! > > I tried setting the httpClientMaxThreads and httpClientMinThreads on the > "to" component, but couldn't get it to work, still stuck at 64 threads. I > Removed the "threads" setting in the route. What am not doing right? > > /jetty:http://localhost:6080/say/hello1?bridgeEndpoint=true&throwExceptionOnFailure=false&disableStreamCache=true&httpClientMinThreads=150&httpClientMaxThreads=190/ > > / Tomas > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Settings-for-threads-per-endpoint-tp5774319p5774340.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
