[
https://issues.apache.org/jira/browse/HTTPCLIENT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565154#action_12565154
]
Roland Weber commented on HTTPCLIENT-741:
-----------------------------------------
My mistake. When I created the adapter, I considered it a single-threading
class because it is handed only to the thread that allocates the connection.
Should have thought about multithreading when writing the abort stuff. I'll
look at the code when I find the time. On the conceptual level, the changes are
good.
cheers,
Roland
> 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]
