I have a consumer :
/jetty:http://localhost:6080/say/hello1?matchOnUriPrefix=true&enableMultipartFilter=false/
And a producer:
/http4://localhost:6080/mdp/api/ifmdp/map?bridgeEndpoint=true&throwExceptionOnFailure=false&disableStreamCache=true/
When my application calls the URL may look like:
/htt
In the end I got around this by using http4 component instead of jetty, and
the component settings
"setConnectionsPerRoute" and "setMaxTotalConnections" combined with the
"threads" setting on the route.
This seems to give me the unlimited number of parallell sessions that I was
after.
--
View
That actually seems to get me to the same place. I can control Max number of
threads up to 64 per Producer, but never above that. Have even tried
implenting my own thread pool, but same result. The setting works, I can see
that, but only up to 64.
Btw, multiple producers give me 64 *
Any other c
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/sa
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 Ro