[
https://issues.apache.org/jira/browse/HTTPCLIENT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565078#action_12565078
]
Oleg Kalnichevski commented on HTTPCLIENT-741:
----------------------------------------------
Another major problem is that AbstractClientConnAdapter attempts to release the
connection upon invocation of the abort method, which essentially requires the
connection manager (or at least its releaseConnection method) to be threading
safe. We should not make such assumption.
Roland
I am going to go ahead and commit fixes for the above problems, given the fact
you may be off-line in the coming days / weeks. Please review the changes when
you happen to have a chance. If you find anything disagreeable, please let me
know.
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]
