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

Oleg Kalnichevski commented on HTTPCLIENT-1228:
-----------------------------------------------

I have run the test over 1000 times but was unable to reproduce the problem on 
my Linux box. I do not have a Mac with OS X 10.8 at my disposal. Is there any 
chance you could try running your test app on a non-Mac platform (Linux, 
Solaris or Windows)?

Oleg
                
> HttpGet.abort() / HttpPost.abort() doesn't always abort immediately
> -------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1228
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1228
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.2.1
>            Reporter: Dennis Ju
>            Priority: Minor
>         Attachments: TestAbort.java
>
>
> HttpGet.abort() and HttpPost.abort() don't always abort immediately. It works 
> most of the time, but occasionally the connection will block until it times 
> out. I noticed this only happens when I explicitly set a timeout value 
> (HttpConnectionParams.setConnectionTimeout()).
> According to HttpComponent docs, "When an HTTP request is aborted its 
> execution thread blocked in an I/O operation is guaranteed to unblock by 
> throwing a InterruptedIOException".
> The attached test code should demonstrate the issue. Every once in awhile, 
> you'll get "Connect to slow.website.com:80 timed out".
> I'm running Mac OS X 10.8 (Java version 1.6.0_29).

--
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