[ 
https://issues.apache.org/jira/browse/HTTPCORE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCORE-289.
----------------------------------------

    Resolution: Fixed

I have found what appears to be a reasonable solution to the problem. Please 
re-test with the latest SVN snapshot.

Oleg
                
> Cancellable#cancel() not invoked when network connection dies
> -------------------------------------------------------------
>
>                 Key: HTTPCORE-289
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-289
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore NIO
>    Affects Versions: 4.2-alpha2
>            Reporter: Geir Harald Hansen
>             Fix For: 4.2-alpha3
>
>         Attachments: Test.java
>
>
> I am rewriting my software to use the new API that comes with 4.2-alpha2. 
> Returning a Cancellable from HttpAsyncRequestHandler#handle() seems like a 
> good idea for long running requests like long polling. But I don't ever see 
> Cancellable#cancel() being called.
> I telnet into my server and type the necessary HTTP to start a long running 
> request. A Cancellable is created and returned from handle(). Then I kill the 
> telnet process, thereby killing the connection. I expect cancel() to be 
> invoked in the connection's Cancellable at this point, but nothing happens. 
> cancel() is not invoked in my Cancellable, and there are no calls to 
> HttpAsyncServiceHandler#closed(), HttpAsyncServiceHandler#exception() or 
> DefaultServerIODispatch#onClosed() either.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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