[ 
https://issues.apache.org/jira/browse/HTTPASYNC-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689061#comment-13689061
 ] 

Mauro Improta commented on HTTPASYNC-39:
----------------------------------------

But the request seems to be completed, exactly like in the successful thread 
http-outgoing-57.
In the previous log file sample I omitted System.out output added by me. As a 
proof of response completion I restore these lines (please consider a possible 
break of sequentiality due to the different logging way). Please find the new 
log file.
The "Request completed" line is written by the completed() method of the 
callback.
Anyway, the output in the exception relates to the second request, started 3 ms 
before. You can see it by means of the request id I added at the beginning of 
the exception output.
                
> 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
>         Attachments: log_stdout.txt, log.txt
>
>
> 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]

Reply via email to