/Jetty-AHC-route-producing-a-lot-of-threads-tp5771106p5771455.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thank you, I'll give this a try without dynamic routes and let you know the
results!
Les
--
View this message in context:
http://camel.465427.n5.nabble.com/Jetty-AHC-route-producing-a-lot-of-threads-tp5771106p5771413.html
Sent from the Camel - Users mailing list archive at Nabble.com.
eaders("CamelHttpPath")
>>>
>>> .toD("ahc:http://localhost:9000/wait/${headers.timeout}?bridgeEndpoint=true";);
>>>
>>> It appears that the AHC component is creating worker threads to manage
>>> outgoing connections to localhost:9000. One
st:9000. One for every connection made to
>> localhost:9090. Am I configuring something wrong, or is this a defect in
>> AHC?
>>
>> Camel version is 2.16-SNAPSHOT
>>
>> Thanks,
>> Les
>>
>>
>>
>>
>> --
>> View this message in
idgeEndpoint=true";);
>
> It appears that the AHC component is creating worker threads to manage
> outgoing connections to localhost:9000. One for every connection made to
> localhost:9090. Am I configuring something wrong, or is this a defect in
> AHC?
>
> Camel version is
eating worker threads to manage
outgoing connections to localhost:9000. One for every connection made to
localhost:9090. Am I configuring something wrong, or is this a defect in
AHC?
Camel version is 2.16-SNAPSHOT
Thanks,
Les
--
View this message in context:
http://camel.465427.n5.nabble.com/Jetty-AH