Sorry to reply you late, I just came back when I was cleaning up the JIRA
issue today.
As you know we don't change the third part dependency version unless it has
some critical bug, I'm afraid you have to use Camel 2.11.0 for the
PoolingClientConnectionManager.
BTW, I just committed the code which
We are still validating Apache Camel 2.11.0, but would you please check
below scenario cause issue or not?
When connection remove from the pool. Are you plane to use
PoolingClientConnectionManager in Apache Camel 2.10.4?
scenario
==
I am more worry about maxTotalConnections connection. If i
I will try using Camel 2.11-SNAPSHOT.
I am more worry about maxTotalConnections connection. If i have 100 routes
and each create 2 connections. we reach the maxTotalConnections. Since we
are not setting connTTL( connection lifetime, <=0 implies "infinity"), so
connection is not remove from connec
The default max connection per route is 20 , if we don't set it the http client
will set it to be 2.
I'm not sure what's kind of use case you need more than 20 connections at the
same time.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | htt
Just a heads up. We upgrade the http client to 4.2.x in Camel 2.11.x,
We are using the PoolingClientConnectionManager instead, as it has much better
default options setting.
Can you try to run you camel route with latest Camel 2.11-SNAPSHOT to see if
the issue is till there?
BTW, I will try to
Thanks for reporting this, I just fill a JIRA[1] for it.
I think we need to provide the options let the user get control of connection
management.
[1]https://issues.apache.org/jira/browse/CAMEL-6026
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.c
