Seeing various locking related question and (almost) always finding the &#39;loop because of spurious wakeups&#39; terms&lt;sup&gt;1&lt;/sup&gt; I wonder, has anyone experienced such kind of a wakeup (assuming a decent hardware/software environment for example)?

I know the term &#39;spurious&#39; means no apparent reason but what can be the reasons for such kind of an event?

(&lt;sup&gt;1&lt;/sup&gt; Note: I&#39;m not questioning the looping practice.)

**Edit:** A helper question (for those who like code samples):

If I have the following program, and I run it:

    public class Spurious {
        public static void main(String[] args) {
            Lock lock = new ReentrantLock();
            Condition cond = lock.newCondition();
            lock.lock();
            try {
                try {
                    cond.await();
                    System.out.println(&quot;Spurious wakeup!&quot;);
                } catch (InterruptedException ex) {
                    System.out.println(&quot;Just a regular interrupt.&quot;);
                }
            } finally {
                lock.unlock();
            }
        }
    }

What can I do to wake this `await` up spuriously without waiting forever for a random event?

All Spurious Wakeup Solutions on Gang of Coders

Total of 1 Spurious Wakeup Solutions

Do spurious wakeups in Java actually happen?