geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Genender (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3613) setConnectionTimeout() does not change the connect timeout on the connector
Date Wed, 21 Nov 2007 13:32:45 GMT

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

Jeff Genender closed GERONIMO-3613.
-----------------------------------

    Resolution: Fixed

Patch applied...thanks!

> setConnectionTimeout() does not change the connect timeout on the connector
> ---------------------------------------------------------------------------
>
>                 Key: GERONIMO-3613
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3613
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
>         Attachments: AsyncHttpClient.patch
>
>
> AsyncHttpClient.setConnectionTimeout() does not change the connect timeout on the connector.
 The SocketConnector object is instantiated in the AsyncHttpClient constructor, and the connectTimeout
instance variable is applied to the configuration in the AsyncHttpClient constructor, and
is never used subsequently.
> setConnectionTimeout() has no effect, and getConnectionTimeout() returns a misleading
value as a result.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message