站内搜索: 请输入搜索关键词
当前页面: 在线文档首页 > JDK 5 Documentation v6.0, Java 2 SDK 英文文档

Uses of Class java.util.concurrent.locks.AbstractQueuedSynchronizer.ConditionObject (Java Platform SE 6) - JDK 5 Documentation v6.0, Java 2 SDK 英文文档


Java™ Platform
Standard Ed. 6

Uses of Class
java.util.concurrent.locks.AbstractQueuedSynchronizer.ConditionObject

Packages that use AbstractQueuedSynchronizer.ConditionObject
java.util.concurrent.locks Interfaces and classes providing a framework for locking and waiting for conditions that is distinct from built-in synchronization and monitors. 
 

Uses of AbstractQueuedSynchronizer.ConditionObject in java.util.concurrent.locks
 

Methods in java.util.concurrent.locks with parameters of type AbstractQueuedSynchronizer.ConditionObject
 Collection<Thread> AbstractQueuedSynchronizer.getWaitingThreads(AbstractQueuedSynchronizer.ConditionObject condition)
          Returns a collection containing those threads that may be waiting on the given condition associated with this synchronizer.
 int AbstractQueuedSynchronizer.getWaitQueueLength(AbstractQueuedSynchronizer.ConditionObject condition)
          Returns an estimate of the number of threads waiting on the given condition associated with this synchronizer.
 boolean AbstractQueuedSynchronizer.hasWaiters(AbstractQueuedSynchronizer.ConditionObject condition)
          Queries whether any threads are waiting on the given condition associated with this synchronizer.
 boolean AbstractQueuedSynchronizer.owns(AbstractQueuedSynchronizer.ConditionObject condition)
          Queries whether the given ConditionObject uses this synchronizer as its lock.
 


Java™ Platform
Standard Ed. 6

Submit a bug or feature
For further API reference and developer documentation, see Java SE Developer Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.

Copyright 2006 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.