wait : Java Glossary


Waiting is much like Thread sleeping. It consumes no cpu cycles. It is not the same thing as a tight test loop. A Thread suspends execution (does nothing), until some other thread gives it the go-ahead to resume execution with a notify().

Object.wait() and Object. notify() are methods used to coordinate Threads. Note these are methods of all objects, not just Threads. These methods are not something you will use directly in ordinary code. For most tasks, you would use one of the classes in the java.util.concurrent package.

Let’s pretend though you were writing some sort of producer-consumer logic from scratch where thread A produced objects for Thread B to consume.

In the ideal situation, with a multiple CPU (Central Processing Unit) machine, both Threads would whip along at full bore, but if B got behind consuming, (full queue), (Lucy in the chocolate factory), then A should wait() for B to catch up and B should notify() A when A can start working again. Similarly if A can’t keep up producing fast enough, (empty queue), B should wait() and A should notify() B when B can start working again.

You need an arbitrary rendezvous object for one Thread to wait() on and the other to notify(). It can get hairier with multiple waiters and multiple notifiers and timeouts on the waits.

Learning More

Oracle’s Javadoc on Object.wait and Object.notify : available:
Oracle’s Javadoc on Thread class : available:

This page is posted
on the web at:


Optional Replicator mirror
of mindprod.com
on local hard disk J:

Please the feedback from other visitors, or your own feedback about the site.
Contact Roedy. Please feel free to link to this page without explicit permission.

Your face IP:[]
You are visitor number