AsyncNHttpServiceHandler does not react when long polling clients disconnect
----------------------------------------------------------------------------
Key: HTTPCORE-272
URL: https://issues.apache.org/jira/browse/HTTPCORE-272
Project: HttpComponents HttpCore
Issue Type: Bug
Components: HttpCore NIO
Affects Versions: 4.1.3
Reporter: Geir Harald Hansen
Priority: Minor
When using NHttpRequestHandler and in its handle() method storing the
NHttpResponseTrigger and HttpResponse for later, to implement long polling,
AsyncNHttpServiceHandler does not react when clients disconnect. It does react
(its close() method is invoked) if other connections are closed, though. Its
close() method is also called later when trying to write to the connection.
Order of events:
1. NHttpRequestHandler.handle() invoked, trigger and response stored
2. Client disconnects - connection goes to CLOSE_WAIT
3. Connection goes out of CLOSE_WAIT and disappears
4. After a few minutes I try to use the NHttpResponseTrigger to send a response
5. Now AsyncNHttpServiceHandler reacts and tells me the connection has closed
It would be useful if AsyncNHttpServiceHandler was told of closed connections
immediately so resources are not wasted preparing data for clients that are no
longer there.
--
This message is automatically generated by JIRA.
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]
