[
https://issues.apache.org/jira/browse/HTTPCLIENT-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788350#comment-17788350
]
Oleg Kalnichevski commented on HTTPCLIENT-2306:
-----------------------------------------------
I _suspect_ the problem is that your code is leaking connections, and not the
connection pool configuration but it is impossible to say with literally no
details about message exchanges involved.
Please note this is the wrong place to ask questions. This is a issue tracker,
not a forum. Please in the future post your questions to the Apache HttpClient
user list [httpclient-us...@hc.apache.org|mailto:httpclient-us...@hc.apache.org]
Oleg
> What is different in PoolingHttpClientConnectionManager from
> MultiThreadedHttpConnectionManager?
> ------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-2306
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2306
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: Documentation, HttpClient (classic)
> Affects Versions: 4.5.13
> Reporter: harsha vardhan sai T
> Priority: Blocker
>
> I would like to learn what is different in the new
> PoolingHttpClientConnectionManager from MultiThreadedHttpConnectionManager.
> I migrated the existing code to the new connection manager by following some
> migration guides. According to documentations
> PoolingHttpClientConnectionManager is the replacement of
> MultiThreadedHttpConnectionManager. Everything works fine but some times
> depending on the application usage I get
> org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for
> connection from pool
> According to
> [https://hc.apache.org/httpclient-legacy/apidocs/constant-values.html#org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.DEFAULT_MAX_TOTAL_CONNECTIONS]
> previously the default max total connections were 20 and max per host was 2.
> We did not set these values too hence I expect these values were in
> previosuly. But with the new connection manager I set it to 100 as maxtotal
> and 50 as maxperroute. I still see the exception coming in and be there until
> I restart.
> Did the old connection manager have limits on max total connections and this
> is different or there is something else that has changed?
>
> Could some one please help me understand?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
