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: [email protected]
For additional commands, e-mail: [email protected]
