wait(), notify() and notifyAll() in Java

来源:互联网 发布:windows media play11 编辑:程序博客网 时间:2024/05/22 17:20

The use of the implicit monitors in Java objects is powerful, but you can achieve a more subtle level of control through inter-process communication. As you will see, this is especially easy in Java.Multithreading replaces event loop programming by dividing your tasks into discrete and logical units. Threads also provide a secondary benefit: they do away with polling. Polling is usually implemented by a loop that is used to check some condition repeatedly. Once the condition is true, appropriate action is taken. This wastes CPU time. For example, consider the classic queuing problem, where one thread is producing some data and another is consuming it. To make the problem more interesting, suppose that the producer has to wait until the consumer is finished before it generates more data. In a polling system, the consumer would waste many CPU cycles while itwaited for the producer to produce. Once the producer was finished, it would start polling, wasting more CPU cycles waiting for the consumer to finish, and so on. Clearly, this situation is undesirable.To avoid polling, Java includes an elegant interrocess communication mechanism via the wait( ), notify( ), and notifyAll( ) methods. These methods are implemented as final methods in Object, so all classes have them. All three methods can be called only from within a synchronized method. Although conceptually advanced from a computer science perspective, the rules for using these methods are actually quite simple: * wait( ) tells the calling thread to give up the monitor and go to sleep until some other thread enters the same monitor and calls notify( ). * notify( ) wakes up the first thread that called wait( ) on the same object. * notifyAll( ) wakes up all the threads that called wait( ) on the same object. The highest priority thread will run first.These methods are declared within Object, as shown here:final void wait( ) throws InterruptedExceptionfinal void notify( )final void notifyAll( )Additional forms of wait( ) exist that allow you to specify a period of time to wait. The following sample program incorrectly implements a simple form of the producer/consumer problem. It consists of four classes: Q, the queue that you're trying to synchronize; Producer, the threaded object that is producing queue entries; Consumer, the threaded object that is consuming queue entries; and PC, the tiny class that creates the single Q, Producer, and Consumer.

 

Although the put( ) and get( ) methods on Q aresynchronized, nothing stops the producer from overrunning the consumer, nor will anything stopthe consumer from consuming the same queue value twice. Thus, you get theerroneous output shown here (the exact output will vary with processor speed and task load):

Put: 1
Got: 1
Got: 1
Got: 1
Got: 1
Got: 1
Put: 2
Put: 3
Put: 4
Put: 5
Put: 6
Put: 7
Got: 7

As you can see, after the producer put 1, the consumer startedand got the same 1 five times in a row. Then, the producer resumed and produced 2through 7 without letting the consumer have a chance to consume them.

The proper way to write this program in Java is to use wait() and notify( ) to signal in both directions, as shown here:

 

 

Inside get( ), wait( ) is called. This causes itsexecution to suspend until the Producernotifies you that some data is ready. When this happens,execution inside get( )resumes. After the data has been obtained, get( ) calls notify(). This tells Producer that it is okay to put more data in the queue. Inside put( ), wait() suspends execution until theConsumer has removed the item from the queue. When executionresumes, the next item of data is put in the queue, and notify( ) iscalled. This tells the Consumer that it should now remove it.

Here is some output from this program, which shows the cleansynchronous behavior:

e
d
Press Control-C to stop.
Put: 0
f
e
c
b
Got: 0
a
d
Put: 1
f
e
c
b
Got: 1
a
d
Put: 2
f
e
c
b
Got: 2
a
d
Put: 3
f
e
c
b
Got: 3
a
d
Put: 4
f
e
c
b
Got: 4
a
d
Put: 5
f
e
c
b
Got: 5
a
d
Put: 6
f
e
c
b
Got: 6
a
d
Put: 7
f
e
c
b
Got: 7
a
d
Put: 8
f
e
c
b
Got: 8
a
d
Put: 9
f
b
Got: 9
a

This tutorial is an extract from the book "The complete Reference Java 2" by Herbert Schildt

 

When used correctly, notify and wait don't need workarounds such as valueSet.

Here's the improved version:
----------------------

 

 

原创粉丝点击