Answer Posted / saurabh m. chande

for wait(), we ask that thread to wait for defined period of time. So, for that defined period of time, CPU just cant sit idle instead it prefers to run another thread which is looking for acquiring a lock by CPU. If wait() don't release the lock, considering the synchronization in mind, it will not serve any purpose but CPU will wait for the defined period being just idle. Then, there is no point of implementing Threads in our application.
sleep() : User is damn sure that he wants to run the thread in sleep mode. So if he uses wait() instead of sleep, then the thread -
1. will wait for defined period of time.
2. when the time is over, thread will go into runnable state and not in running state.
3. not sure when CPU will pick up this thread for further execution.
To avoid all the 3 reasons, sleep will not leave the lock on the thread. Instead it prefers to keep the lock on the thread even if it is in sleep mode. But it is sure that, once the sleep mode is over, it is having a lock and can directly put the thread in running state without further waiting.

- Saurabh M. Chande

How can I swap two variables without using a third variable?

914

---

What are the authentication modes in asp.net? : java security

886

---

What is dto layer in java?

814

---

What is dto in java?

848

---

What is microservices java?

835

---

Why are command line arguments passed as a string?

871

---

Do I need both jdk and jre?

944

---

What is the use of servlet in java?

892

---

Can an application have multiple classes having main method?

869

---

What do you understand by numeric promotion?

948

---

What is meant by swing in java?

886

---

Is php faster than java?

813

---

What is singleton pattern in java?

801

---

Is lambda cheaper than ec2?

867

---

What is stateful in java?

899

---