harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Qiu (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HARMONY-6300) Thread safety bug in Observable
Date Mon, 10 Aug 2009 01:24:14 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sean Qiu reassigned HARMONY-6300:

    Assignee: Sean Qiu

> Thread safety bug in Observable
> -------------------------------
>                 Key: HARMONY-6300
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6300
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>    Affects Versions: 5.0M10
>         Environment: N/A
>            Reporter: Imran Ghory
>            Assignee: Sean Qiu
>            Priority: Minor
> In the RI Observable.java setChanged() & hasChanged()  are synchronized to guarantee
visibility of changed status across threads. 
> This isn't the case in the Harmony Observable. 
> This could be fixed by either setChanged()/hasChanged() being made synchronized or the
changed variable volatile, otherwise one thread could change the observable without it being
visible to other threads. 
> Although the specification  for the Observable class  doesn't specifically say that changes
to Change status will be visible across all threads, it seems to be implied in the statement
 "subclasses may ... deliver notifications on separate threads".

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message