By Russell Walker,2014-09-17 15:25
9 views 0




日期,7/3/2001 10:03:12 AM

7) Threads

Objective 1)

    Write code to define, instantiate and start new threads using both java.lang.Thread and java.lang.Runnable

? Java is fundamentally multi-threaded.

    ? Every thread corresponds to an instance of java.lang.Thread class or a sub-class.

    ? A thread becomes eligible to run, when its start() method is called. Thread scheduler co-

    ordinates between the threads and allows them to run.

    ? When a thread begins execution, the scheduler calls its run method.

Signature of run method public void run()

    ? When a thread returns from its run method (or stop method is called deprecated in 1.2), its

    dead. It cannot be restarted, but its methods can be called. (its just an object no more in a running state)

    ? If start is called again on a dead thread, IllegalThreadStateException is thrown.

    ? When a thread is in running state, it may move out of that state for various reasons. When it becomes eligible for execution again, thread scheduler allows it to run.

? There are two ways to implement threads.

1. Extend Thread class

    public class Thread extends Object implements Runnable


     Thread(Runnable target)

     Thread(Runnable targe, String name)

     Thread(String name)

     Thread(ThreadGroup group, Runnable target)

     Thread(ThreadGroup group, Runnable target, String name)

     Thread(ThreadGroup group, String name)

    ? Create a new class, extending the Thread class.

    ? Provide a public void run method, otherwise empty run in Thread class will be executed.

? Create an instance of the new class.

? Call start method on the instance (dont call

run it will be executed on the same thread)

2. Implement Runnable interface

public interface Runnable

     only one method: public void run

    ? Create a new class implementing the Runnable interface.

? Provide a public void run method.

? Create an instance of this class.

    ? Create a Thread, passing the instance as a target new Thread(object)

    ? Target should implement Runnable, Thread class implements it, so it can be a target itself.

? Call the start method on the Thread.

    ? JVM creates one user thread for running a program. This thread is called main thread. The main method of the class is called from the main thread.

    It dies when the main method ends. If other user threads have been spawned from the main thread, program keeps running even if main thread dies. Basically a program runs until all the user threads (non-daemon threads) are dead.

    ? A thread can be designated as a daemon thread by calling setDaemon(boolean) method. This method should be called before the thread is started, otherwise IllegalThreadStateException will be thrown.

    ? A thread spawned by a daemon thread is a

daemon thread.

    ? Threads have priorities. Thread class have constants MAX_PRIORITY (10), MIN_PRIORITY (1), NORM_PRIORITY (5)

    ? A newly created thread gets its priority from the creating thread. Normally itll be


? getPriority and setPriority are the methods to

    deal with priority of threads.

    ? Java leaves the implementation of thread scheduling to JVM developers. Two types of scheduling can be done.

1. Pre-emptive Scheduling.

Ways for a thread to leave running state -

    ? It can cease to be ready to execute ( by calling a blocking i/o method)

? It can get pre-empted by a high-priority

    thread, which becomes ready to execute.

? It can explicitly call a thread-scheduling

    method such as wait or suspend.

? Solaris JVMs are pre-emptive.

? Windows JVMs were pre-emptive until Java


2. Time-sliced or Round Robin Scheduling

    ? A thread is only allowed to execute for a certain amount of time. After that, it has to

    contend for the CPU (virtual CPU, JVM) time with other threads.

? This prevents a high-priority thread mono-

    policing the CPU.

? The drawback with this scheduling is it

    creates a non-deterministic system at any point

    in time, you cannot tell which thread is running and how long it may continue to run.

? Mactinosh JVMs

? Windows JVMs after Java 1.0.2

Of the two methods of creating a new thread the use

    of Runnable is probably more common. The other method for creating a thread is to create a class that is descended from Thread. This is easy to do but it means you cannot inherit from any other class,

Objective 2)

Recognize conditions that might prevent a thread

    from executing.

? Different states of a thread:

1. Yielding

    ? Yield is a public static void method. Operates on current thread. For static method, call Thread.yield() is ok, dont need call t.yield(),

    where t is instance of Thread, but compiler will

    pass it.

? Moves the thread from running to ready state.

    ? If there are no threads in ready state, the yielded thread may continue execution, otherwise it may have to compete with the other threads to run.

? Run the threads that are doing time-consuming

    operations with a low priority and call yield periodically from those threads to avoid those threads locking up the CPU.

2. Sleeping

? Sleep is also a public static void method.

? Sleeps for a certain amount of time. (passing

    time without doing anything and w/o using CPU)

? Two overloaded versions one with

    milliseconds, one with milliseconds and nanoseconds.

    ? Throws an InterruptedException.(must be caught)

? After the time expires, the sleeping thread

    goes to ready state. It may not execute immediately after the time expires. If there are other threads in ready state, it may have to compete with those threads to run. The correct statement is the sleeping thread would execute some time after the specified time period has elapsed.

    ? If interrupt method is invoked on a sleeping thread, the thread moves to ready state. The next time it begins running, it executes the InterruptedException handler.

3. Suspending

? Suspend and resume are instance methods and

    are deprecated in 1.2

    ? A thread that receives a suspend call, goes to

    suspended state and stays there until it receives a resume call on it.

    ? A thread can suspend it itself, or another thread can suspend it.

    ? But, a thread can be resumed only by another thread.

    ? Calling resume on a thread that is not suspended has no effect.

    ? Compiler wont warn you if suspend and resume are successive statements, although the thread may not be able to be restarted.

4. Blocking

    ? Methods that are performing I/O have to wait for some occurrence in the outside world to happen before they can proceed. This behavior is blocking.

    ? If a method needs to wait an indeterminable amount of time until some I/O takes place, then the

    thread should graciously step out of the CPU. All Java I/O methods behave this way.

    ? A thread can also become blocked, if it failed to acquire the lock of a monitor.

5. Waiting

    ? wait, notify and notifyAll methods are not called on Thread, theyre called on Object. Because the object is the one which controls the threads in this case. It asks the threads to wait and then notifies when its state changes. Its called a


    ? Wait puts an executing thread into waiting state.(to the monitors waiting pool)

? Notify moves one thread in the monitors

    waiting pool to ready state. We cannot control which thread is being notified. notifyAll is recommended.

? NotifyAll moves all threads in the monitors

    waiting pool to ready.

    ? These methods can only be called from synchronized code, or an

    IllegalMonitorStateException will be thrown. In other words, only the threads that obtained the objects lock can call these methods.

The sleep method is static and pauses execution for

    a set number of milliseconds. There is a version that is supposed to pause for a set number of nanoseconds, Here is an example of putting a Thread to sleep, note how the sleep method throws InterruptedException.

public class TSleep extends Thread{

public static void main(String argv[]){

     TSleep t = new TSleep();



     public void run(){







     }catch(InterruptedException ie){}



Objective 3)

    Write code using synchronized wait notify and notifyAll to protect against concurrent access problems and to communicate between threads. Define the interaction between threads and between threads and object locks when executing synchronized wait notify or notifyAll.

Locks, Monitors and Synchronization

? Every object has a lock (for every

    synchronized code block). At any moment, this lock is controlled by at most one thread.

? A thread that wants to execute an objects

    synchronized code must acquire the lock of the

    object. If it cannot acquire the lock, the thread goes into blocked state and comes to ready only when the objects lock is available.

    ? When a thread, which owns a lock, finishes executing the synchronized code, it gives up the lock.

    ? Monitor is an object that can block and revive threads, an object that controls client threads. Asks the client threads to wait and notifies them

    when the time is right to continue, based on its state. In strict Java terminology, any object that has some synchronized code is a monitor.

? 2 ways to synchronize:

1. Synchronize the entire method

? Declare the method to be synchronized - very

    common practice.

? Thread should obtain the objects lock.

2. Synchronize part of the method

    ? Have to pass an arbitrary object which lock is to be obtained to execute the synchronized code block (part of a method).

Synchronized(target) {statements}

? We can specify this in place object, to

    obtain very brief locking not very common

? If target is null, then the

    NullPointerException is thrown.

? wait points to remember

? calling thread gives up CPU

? calling thread gives up the lock

? calling thread goes to monitors waiting pool

    ? wait also has a version with timeout in milliseconds. Use this if youre not sure when the

    current thread will get notified, this avoids the thread being stuck in wait state forever.

? notify points to remember

Report this document

For any questions or suggestions please email