Philip Helger created HTTPCLIENT-2314:
-----------------------------------------
Summary: IllegalStateException: Endpoint is not connected
Key: HTTPCLIENT-2314
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2314
Project: HttpComponents HttpClient
Issue Type: Improvement
Components: HttpClient (classic)
Affects Versions: 5.3, 5.2
Reporter: Philip Helger
Using `PoolingHttpClientConnectionManager`, under high traffic situations it
occurs consistently that the exception "Endpoint is not connected" is invoked.
The full stacktrace looks like this:
{{Caused by: java.lang.IllegalStateException: Endpoint is not connected}}
{{ at org.apache.hc.core5.util.Asserts.check(Asserts.java:38)
~[httpcore5-5.2.4.jar:5.2.4]}}
{{ at
org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager$InternalConnectionEndpoint.getValidatedPoolEntry(PoolingHttpClientConnectionManager.java:664)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager$InternalConnectionEndpoint.setSocketTimeout(PoolingHttpClientConnectionManager.java:697)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.InternalExecRuntime.execute(InternalExecRuntime.java:211)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.MainClientExec.execute(MainClientExec.java:116)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:188)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:192)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:113)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ContentCompressionExec.execute(ContentCompressionExec.java:152)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.RedirectExec.execute(RedirectExec.java:116)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.InternalHttpClient.doExecute(InternalHttpClient.java:170)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:245)
~[httpclient5-5.3.jar:5.3]}}
{{ at
org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:188)
~[httpclient5-5.3.jar:5.3]}}
Unfortunately I don't have a standalone example to reproduce it.
Any suggestions for a workaround????
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
