[
https://issues.apache.org/jira/browse/HTTPCLIENT-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960959#comment-15960959
]
Oleg Kalnichevski commented on HTTPCLIENT-1838:
-----------------------------------------------
No, there are no known issues. There is a multitude of reasons why connections
can end up in the CLOSE_WAIT state and unless I am able to reproduce the issue
in a controlled environment and unambiguously trace the cause of the issue to a
defect in HttpClient code there is not much I can do to help you.
Oleg
> HttpClient leaves connection in CLOSE_WAIT in a multithreaded environment
> -------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1838
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1838
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.3
> Environment: Centos6.3. Apache HttpClient 4.5.3.
> Reporter: kumaran
> Fix For: 4.5.4
>
> Attachments: CvHttpClientImpl.txt
>
>
> We use HttpClient for all our internal http communications and below the code
> snippet,
> val client: CloseableHttpClient = HttpClients.custom()
> .setConnectionManager(clientConnectionManager)
> .setRetryHandler(httpRequestRetryHandler)
> .setDefaultCredentialsProvider(basicCredentialsProvider)
> .evictExpiredConnections()
> .evictIdleConnections(5, TimeUnit.SECONDS)
> .build()
> Sometimes we could see a connection is created but not used and left in
> CLOSE_WAIT state. we couldnt able to find the exact flow, since it happens
> randomly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
