Causes the current thread to wait until it is signalled or {@linkplain Thread#interrupt interrupted}.
The lock associated with this {@code Condition} is atomicallyreleased and the current thread becomes disabled for thread scheduling purposes and lies dormant until one of four things happens:
- Some other thread invokes the {@link #signal} method for this{@code Condition} and the current thread happens to be chosen as thethread to be awakened; or
- Some other thread invokes the {@link #signalAll} method for this{@code Condition}; or
- Some other thread {@linkplain Thread#interrupt interrupts} thecurrent thread, and interruption of thread suspension is supported; or
- A "spurious wakeup" occurs.
In all cases, before this method can return the current thread must re-acquire the lock associated with this condition. When the thread returns it is guaranteed to hold this lock.
If the current thread:
- has its interrupted status set on entry to this method; or
- is {@linkplain Thread#interrupt interrupted} while waitingand interruption of thread suspension is supported,
then {@link InterruptedException} is thrown and the current thread'sinterrupted status is cleared. It is not specified, in the first case, whether or not the test for interruption occurs before the lock is released.
Implementation Considerations
The current thread is assumed to hold the lock associated with this {@code Condition} when this method is called.It is up to the implementation to determine if this is the case and if not, how to respond. Typically, an exception will be thrown (such as {@link IllegalMonitorStateException}) and the implementation must document that fact.
An implementation can favor responding to an interrupt over normal method return in response to a signal. In that case the implementation must ensure that the signal is redirected to another waiting thread, if there is one.
@throws InterruptedException if the current thread is interrupted(and interruption of thread suspension is supported)