[
https://issues.apache.org/jira/browse/HTTPCLIENT-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-682.
------------------------------------------
Resolution: Invalid
Wolfgang
You are confusing a connection manager timeout with a connect timeout.
Connection manager timeout is not applicable to the Simple HTTP connection
manager because it never blocks waiting for a connection to become available in
the connection pool. It always returns the same connection object without
blocking.
Oleg
> ConnectionManager timeout not used
> ----------------------------------
>
> Key: HTTPCLIENT-682
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-682
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 3.0.1
> Reporter: Wolfgang Winter
>
> In HttpClientParams a connectionManagerTimeout can be set but is never used.
> The HttpClient uses per default the SimpleHttpConnectionManager, this class
> implements method getConnectionWithTimeout(
> HostConfiguration hostConfiguration, long timeout). However, the
> parameter timeout is not used in the method, despite it's name. The timeout
> parameter is set with HttpClientParams.connectionManagerTimeout, therefore it
> is of no use in the standard framework.
> you can fix this by
> --> correcting the method
> SimpleHttpConnectionManager.getConnectionWithTimeout()
> --> extending the Javadoc of
> SimpleHttpConnectionManager.getConnectionWithTimeout() and
> HttpClientParams.setConnectionManagerTimeout() saying, that the timeout
> parameter is not used in the standard default implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
