hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPASYNC-7) Possible race condition in BasicFuture
Date Sun, 11 Sep 2011 20:10:08 GMT

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

Oleg Kalnichevski commented on HTTPASYNC-7:

Rolf, are you sure about that? Both methods are synchronized so only one of them can mutate
the internal state of the object at a time and the sequence of modification of the 'completed'
and 'result' instance variables should not matter. 


> 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