hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rolf Kalbermatter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPASYNC-7) Possible race condition in BasicFuture
Date Mon, 12 Sep 2011 17:32:08 GMT

    [ https://issues.apache.org/jira/browse/HTTPASYNC-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102824#comment-13102824

Rolf Kalbermatter commented on HTTPASYNC-7:

You are of course right. I completely overlooked the synchronized attribute of those methods.
And removing that attribute seems no option even if the order of the method calls would be
changed, so I suppose this is a non issue, or at most a cosmetic one. 

> Possible race condition in BasicFuture
> --------------------------------------
>                 Key: HTTPASYNC-7
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-7
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>    Affects Versions: 4.0-alpha2
>         Environment: Java source code
>            Reporter: Rolf Kalbermatter
>              Labels: features
>             Fix For: 4.0-alpha3
>   Original Estimate: 10m
>  Remaining Estimate: 10m
> In the complete() method inside the BasicFuture class exists a possible race condition
at line 98 and 99. First the "completed" status is set to true and after that the "result"
is assigned. However in the get methods the completed status is checked and then the result
returned, resulting in the potential race condition that the still unassigned result is returned.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message