[
https://issues.apache.org/jira/browse/HTTPCLIENT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565092#action_12565092
]
Oleg Kalnichevski commented on HTTPCLIENT-741:
----------------------------------------------
AbstractClientConnAdapter#abortConnection() no longer releases the wrapped
connection back to the connection manager. The wrapped connection gets shut
down, but remains attached to the adapter. The connection is expected to be
released back to the connection manager by the request execution thread.
Roland,
Please review and approve the changes when you happen to have a chance.
Sam,
I believe the issue has been resolved. Could you please re-test your code
against the latest SVN snapshot and confirm the problem is gone? If the problem
still persists, please do post stack traces, the more the better.
Oleg
> AbstractClientConnAdapter prone to concurrency issues
> -----------------------------------------------------
>
> Key: HTTPCLIENT-741
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-741
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 4.0 Alpha 2
> Reporter: Oleg Kalnichevski
> Priority: Critical
> Fix For: 4.0 Alpha 3
>
>
> AbstractClientConnAdapter is currently prone to all sorts of concurrency
> issues. (1) Access to internal state is not properry synchronized making the
> class prone to race conditions. Presently none of the instance variables is
> even declared volatile. (2) AbstractClientConnAdapter treats aborted
> connection as one in an illegal state, which is not quite right.
> Oleg
--
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]
