hg: jdk7/tl/jdk: 6801020: Concurrent Semaphore release may cause some require thread not signaled (original) (raw)
martinrb at google.com martinrb at google.com
Thu Mar 26 22:09:22 UTC 2009
- Previous message: hg: jdk7/tl/jdk: 6819122: DefaultProxySelector should lazily initialize the Pattern object and the NonProxyInfo objects
- Next message: hg: jdk7/tl/jdk: 6822903: Reliability and documentation improvements for ReentrantReadWriteLock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Changeset: 5303aece2068 Author: dl Date: 2009-03-26 11:59 -0700 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/5303aece2068
6801020: Concurrent Semaphore release may cause some require thread not signaled Summary: Introduce PROPAGATE waitStatus Reviewed-by: martin
! src/share/classes/java/util/concurrent/locks/AbstractQueuedLongSynchronizer.java ! src/share/classes/java/util/concurrent/locks/AbstractQueuedSynchronizer.java
- test/java/util/concurrent/Semaphore/RacingReleases.java
- Previous message: hg: jdk7/tl/jdk: 6819122: DefaultProxySelector should lazily initialize the Pattern object and the NonProxyInfo objects
- Next message: hg: jdk7/tl/jdk: 6822903: Reliability and documentation improvements for ReentrantReadWriteLock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]