Java concurrency provides two methods, sleep() and wait() for controlling the execution flow of threads. While both methods appear similar in purpose, they play different roles.
In this Java tutorial, we will learn the difference between sleep() and wait() methods. We will also learn when to use which method and what effect they bring in Java concurrency.
1. Java Thread.sleep() Method
The Thread.sleep() is a static method that temporarily suspends its execution of the current thread for a specified time duration. During this time, the thread remains in the TIMED_WAITING state.
- The sleep() method is best used in scenarios when we want to delay the execution of a thread for a specific period while waiting for a resource.
- It is quite common to use sleep() method for simulating a time-consuming operation or a time interval between tasks during unit testing.
import java.time.LocalDateTime;
public class SleepExample {
public static void main(String[] args) {
LocalDateTime start = LocalDateTime.now();
System.out.println("Thread started at: " + start);
try {
Thread.sleep(2000); // Sleep for 2 seconds
} catch (InterruptedException e) {
e.printStackTrace();
}
LocalDateTime end = LocalDateTime.now();
System.out.println("Thread resumed after sleep at: " + end);
}
}
The program output:
Thread started at: 2022-05-12T09:30:45.123456
Thread resumed after sleep at: 2022-05-12T09:30:47.125789
In this example, the thread started at 2022-05-12T09:30:45.123456 and resumed after sleeping for 2 seconds at 2022-05-12T09:30:47.125789. The actual timestamps will depend on the current time when the program is executed.
As the
sleep()is astaticmethod which means that it always affects the current thread (the one that is executing the sleep method).A common mistake is to call
t.sleep()wheretis a different thread; even then, it is the current thread that will sleep, not thetthread.
2. Java Object.wait() Method
The wait() method is a non-static method defined in the Object class and used for inter-thread communication and synchronization. When a thread invokes wait() on an object, it releases the lock on the object and enters the WAITING state until another thread notifies it using the notify() or notifyAll() methods.
We use the wait() method generally to solve the producer-consumer pattern or other synchronization scenarios.
import java.time.LocalDateTime;
public class WaitExample {
public static void main(String[] args) {
Object lock = new Object();
LocalDateTime start = LocalDateTime.now();
System.out.println("Thread started at: " + start);
Thread waitingThread = new Thread(() -> {
synchronized (lock) {
try {
System.out.println("Waiting for notification at: " + LocalDateTime.now());
lock.wait(); // Wait until notified
System.out.println("Notification received at: " + LocalDateTime.now());
} catch (InterruptedException e) {
e.printStackTrace();
}
}
});
Thread notifyingThread = new Thread(() -> {
synchronized (lock) {
try {
Thread.sleep(2000); // Simulate some processing time
lock.notify(); // Notify waiting thread
System.out.println("Notification sent at: " + LocalDateTime.now());
} catch (InterruptedException e) {
e.printStackTrace();
}
}
});
waitingThread.start();
notifyingThread.start();
// Wait for threads to finish
try {
waitingThread.join();
notifyingThread.join();
} catch (InterruptedException e) {
e.printStackTrace();
}
LocalDateTime end = LocalDateTime.now();
System.out.println("Thread finished at: " + end);
}
}
In this example:
- The program starts and prints the start timestamp.
- The waiting thread starts and prints the waiting timestamp.
- The notifying thread sends the notification after 2 seconds and prints the notification timestamp.
- The waiting thread receives the notification and prints the received timestamp.
- The program finishes and prints the finish timestamp.
The actual timestamps will depend on the current time wh
The program output:
Thread started at: 2022-05-12T09:30:45.123456
Waiting for notification at: 2022-05-12T09:30:45.123456
Notification sent at: 2022-05-12T09:30:47.125789
Notification received at: 2022-05-12T09:30:47.125789
Thread finished at: 2022-05-12T09:30:47.125789
Read more : Working with wait() and notify()
3. Difference between wait() and sleep() Method
The major difference is that wait() releases the lock or monitor while sleep() doesn’t release the lock while waiting. The wait() is used for inter-thread communication while sleep() is used to introduce pause on execution, generally.
The following table summarizes the main differences between the wait() and sleep() methods:
| Feature | wait() | sleep() |
|---|---|---|
| Method Location | Defined in the Object class | Defined in the Thread class |
| Usage | Used for inter-thread communication and synchronization | Used to pause the execution of a thread |
| Lock Release | Releases the lock on the object being waited on | Does not release the lock |
| Object Dependency | Called on an object within a synchronized block | Called directly on the Thread object |
| Interruption | Throws InterruptedException when interrupted | Also throws InterruptedException when interrupted |
| Notification | Requires notify() or notifyAll() to resume execution | Not applicable, thread resumes automatically after sleep |
| Associated State | Puts the thread in the WAITING or TIMED_WAITING state | Puts the thread in the TIMED_WAITING state |
| Time Specification | No time duration specified | Time duration specified in milliseconds |
Read more : Difference between yield() and join()
4. Summary
Let’s categorize all the above points in short to remember.
4.1. Method called on
wait()– Call on an object; the current thread must synchronize on the lock object.sleep()– Call on a Thread; always currently executing thread.
4.2. Synchronized
wait()– when synchronized multiple threads access same Object one by one.sleep()– when synchronized multiple threads wait for sleep over of sleeping thread.
4.3. Lock duration
wait()– release the lock for other objects to have chance to execute.sleep()– keep lock for at least t times if timeout specified or somebody interrupt.
4.4. wake up condition
wait()– until call notify(), notifyAll() from objectsleep()– until at least time expire or call interrupt().
4.5. Usage
sleep()– for time-synchronizationwait()– for multi-thread-synchronization.
Hope the above information will add some value in your knowledge-base.
Happy Learning !!
which one hits a performance ? sleep or wait ?
Awesome explanation. Thanks keep up the good work and knowledge sharing.
it’s true
Great tutorial, thanks!
Very informative article. Thanks
Good Article..Really useful
Hi Lokesh,
many thanks for your valuable posts .
The only site I refer for any java queries is this !!!!!!!!!!
Hi Lokesh,
Nice article. Please explain/add yield() and join() method to this article as sometime this 4 api looks similar yet so diffrent.
I added it to my TODO list.
I have found the article very clear and explanatory.
you write in easy way…really you are doing good job ..james gosling invented java and lokesh is making easyjava :)
:-)
Hi.. I have a question!!!
Why wait(), notift(),notifyAll() always works in Synchronized Block?
Puneet, because it was designed in this way only. These methods were introduced as means of making safe interactions between threads. If they were allowed without synchronization, there were occur lots of other problems such as race condition, data corruption and even program crash.
Please note that a program does not get any kind of surety from low level OS thread scheduling, so it depends on language runtime to manage its thread.
Thanks for the answer Lokesh..
I have 1 more question!!!
why wait(), notift(),notifyAll() are the methods of Object class, insteed of Thread Class?
Pardon for being lazy here, just came from office. You can get a good explanation here:
https://stackoverflow.com/questions/17840397/concept-behind-putting-wait-notify-methods-in-object-class
It is so because, Thread 2 will not have the idea of Thread 1 state, where t1 is in wait state or it is notified. That’s why there methods are of Object class. please let me know, if i am wrong.
I will say partly because real problem is to find out which all threads are in application and then which one are waiting on current monitor.
Lokesh, What happens if someone dosent call notify( earlier thread called wait) ?
will this keep the program in hanged state? will it not allow program to exit/terminate?
Tricky question.. In my view, no major impact on application just because one of several hundreds thread is blocked somewhere. Rest of application will run fine. This is very much clear and easy.
No, program will not hang. According to theory, it should not allow to terminate and you might need to do it forcefully.
Good points you are covering here, it will be more helpful if you take up the relatively new topics like concurrent package, annotations, generics, nio etc
Sure, I will take up these topics in near future..