Andreas L. Delmelle <[EMAIL PROTECTED]> changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED

--- Comment #1 from Andreas L. Delmelle <[EMAIL PROTECTED]>  2008-11-14 
10:12:09 PST ---

I think the gist is correct. Have you tried changing it? Does it resolve the
issue if you do?
Reason I'm asking is that there seems to be another problem: changeLock is not
a 'final' variable, nor is it declared 'volatile'. 
As a consequence:
a) since it is neither final nor volatile, it is not guaranteed to be properly
initialized (some threads may see 'null' instead of the Object instance)
b) since it is not final, it is theoretically possible to re-assign the
changeLock member to a different instance, which would lead to unpredictable
behavior. It is possible for two threads to enter the synchronized block, since
they have each locked a separate instance.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to