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

Posted to dev@hc.apache.org by "Clinton Nielsen (JIRA)" <ji...@apache.org> on 2013/04/12 17:04:16 UTC

[jira] [Created] (HTTPASYNC-39) SocketTimeoutException occurs too soon

Clinton Nielsen created HTTPASYNC-39:
----------------------------------------

             Summary: SocketTimeoutException occurs too soon
                 Key: HTTPASYNC-39
                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-39
             Project: HttpComponents HttpAsyncClient
          Issue Type: Bug
    Affects Versions: 4.0-beta3
            Reporter: Clinton Nielsen


In a highly concurrent environment, where SocketTimeout is set to 30,000 milliseconds, we are often seeing a timeoutexception after only 0 or 1 or 2 milliseconds has actually passed.

I get the impression that in the AbstractIOReactor timeoutCheck function, session.getLastAccessTime is being called on the session before the lastAccessTime is set on the session for the current session (ie. the lastAccessTime being retrieved is the time that was set on the session object for the previous http session)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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