You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2017/11/17 17:07:00 UTC

[jira] [Resolved] (HTTPCLIENT-1879) connection should revert to SocketConfig's soTimeout

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-1879.
-------------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.0 Alpha3
                   4.6 Alpha1
                   4.5.4

Fixed in 4.5.x and 4.6.x branches. 

In 5.x I implemented a more generic mechanism of activation / passivation of managed connections that is presently used to restore original socket timeout value upon connection lease from the pool.

Oleg

> connection should revert to SocketConfig's soTimeout
> ----------------------------------------------------
>
>                 Key: HTTPCLIENT-1879
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1879
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.3
>            Reporter: Xiaoshuang LU
>             Fix For: 4.5.4, 4.6 Alpha1, 5.0 Alpha3
>
>
> DefaultHttpClientConnectionOperator sets SO_TIMEOUT when creating sockets. However, MainClientExec may overwrite this option in execute method (line 248). It seems that we need to revert this option to the original value before releasing connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org