6307490: (spec thread) Thread.State or related doc should clarify valid

David Holmes - Sun Microsystems David.Holmes at Sun.COM
Fri Jun 8 04:47:55 PDT 2007


I've updated the CR. The current behaviour (which as of Java 6 is 
uniform across all platforms) of reporting WAITING is definitely a 
violation of the current spec - which states:

public static final Thread.State BLOCKED

    Thread state for a thread blocked waiting for a monitor lock. A
    thread in the blocked state is waiting for a monitor lock to enter
    a synchronized block/method or *reenter a synchronized block/method
    after calling Object.wait.*

David Holmes

Martin Buchholz said the following on  8/06/07 05:10 PM:
> I've come to suspect that this bug:
> 
> 6307490: (spec thread) Thread.State or related doc should clarify valid
> notifyAll behavior
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6307490
> 
> belongs to the hotspot runtime team.
> Could someone evaluate that?
> Y'all are invited to take ownership.
> 
> Thanks,
> 
> Martin



More information about the hotspot-runtime-dev mailing list