AbstractClientConnAdapter#abortConnection() does not release the connection if
called from the main execution thread while there is no blocking I/O operation
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: HTTPCLIENT-763
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-763
Project: HttpComponents HttpClient
Issue Type: Bug
Components: HttpConn
Affects Versions: 4.0 Alpha 3
Reporter: Oleg Kalnichevski
Fix For: 4.0 Alpha 4
#abortConnection() is usually expected to be called from a helper thread in
order to unblock the main execution thread blocked in an I/O operation. It may
be unsafe to call #releaseConnection() from the helper thread, so we have to
rely on an IOException thrown by the closed socket on the main thread to
trigger the release of the connection back to the connection manager. However,
if this method is called from the main execution thread it should be safe to
release the connection immediately. Besides, this also helps ensure the
connection gets released back to the manager if #abortConnection() is called
from the main execution thread while there is no blocking I/O operation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
