You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Richie Jefts (JIRA)" <ji...@apache.org> on 2008/01/17 20:27:34 UTC

[jira] Created: (HTTPCORE-141) DefaultConnectingIOReactor incorrectly handles connection timeout

DefaultConnectingIOReactor incorrectly handles connection timeout
-----------------------------------------------------------------

                 Key: HTTPCORE-141
                 URL: https://issues.apache.org/jira/browse/HTTPCORE-141
             Project: HttpComponents Core
          Issue Type: Bug
    Affects Versions: 4.0-alpha6
            Reporter: Richie Jefts


In DefaultConnectingIOReactor.processTimeouts() the session request correctly notifies the callback of a timeout but the SelectionKey is not cancelled. This causes multiple session request callbacks for a connection timeout since each iteration through processEvents() will still check this SelectionKey for a timeout that has already occurred.

-- 
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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] Updated: (HTTPCORE-141) DefaultConnectingIOReactor incorrectly handles connection timeout

Posted by "Richie Jefts (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPCORE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richie Jefts updated HTTPCORE-141:
----------------------------------

    Priority: Minor  (was: Major)

> DefaultConnectingIOReactor incorrectly handles connection timeout
> -----------------------------------------------------------------
>
>                 Key: HTTPCORE-141
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-141
>             Project: HttpComponents Core
>          Issue Type: Bug
>    Affects Versions: 4.0-alpha6
>            Reporter: Richie Jefts
>            Priority: Minor
>
> In DefaultConnectingIOReactor.processTimeouts() the session request correctly notifies the callback of a timeout but the SelectionKey is not cancelled. This causes multiple session request callbacks for a connection timeout since each iteration through processEvents() will still check this SelectionKey for a timeout that has already occurred.

-- 
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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] Resolved: (HTTPCORE-141) DefaultConnectingIOReactor incorrectly handles connection timeout

Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPCORE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCORE-141.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0-beta1

Richie,

I think the initial intension was to allow the timeout period to be extended without canceling the request. This, however, does not seem to make sense, as the only possibility to do so is by resetting the timeout value in the SessionRequestCallback, which is optional and may be omitted.

Fixed in the SVN trunk.

Oleg 

> DefaultConnectingIOReactor incorrectly handles connection timeout
> -----------------------------------------------------------------
>
>                 Key: HTTPCORE-141
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-141
>             Project: HttpComponents Core
>          Issue Type: Bug
>    Affects Versions: 4.0-alpha6
>            Reporter: Richie Jefts
>            Priority: Minor
>             Fix For: 4.0-beta1
>
>
> In DefaultConnectingIOReactor.processTimeouts() the session request correctly notifies the callback of a timeout but the SelectionKey is not cancelled. This causes multiple session request callbacks for a connection timeout since each iteration through processEvents() will still check this SelectionKey for a timeout that has already occurred.

-- 
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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org