While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.
Understanding Thread Life Cycle in Java and Thread States are very important when you are working with Threads and programming for multithreaded environment. From our last tutorial, we can create a java thread class by implementing Runnable interface or by extending Thread class, but to start a java thread, we first have to create the Thread object and call it’s start() method to execute run() method as a thread.
Below diagram shows different states of thread life cycle in java. We can create a thread in java and start it but how the thread states change from Runnable to Running to Blocked depends on the OS implementation of thread scheduler and java doesn’t have full control on that.
When we create a new Thread object using new operator, thread state is New Thread. At this point, thread is not alive and it’s a state internal to Java programming.
When we call start() function on Thread object, it’s state is changed to Runnable. The control is given to Thread scheduler to finish it’s execution. Whether to run this thread instantly or keep it in runnable thread pool before running, depends on the OS implementation of thread scheduler.
When thread is executing, it’s state is changed to Running. Thread scheduler picks one of the thread from the runnable thread pool and change it’s state to Running. Then CPU starts executing this thread. A thread can change state to Runnable, Dead or Blocked from running state depends on time slicing, thread completion of run() method or waiting for some resources.
A thread can be waiting for other thread to finish using thread join or it can be waiting for some resources to available. For example producer consumer problem or waiter notifier implementation or IO resources, then it’s state is changed to Waiting. Once the thread wait state is over, it’s state is changed to Runnable and it’s moved back to runnable thread pool.
Once the thread finished executing, it’s state is changed to Dead and it’s considered to be not alive. Above are the different states of thread. It’s good to know them and how thread changes it’s state. That’s all for thread life cycle in java.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in our Questions & Answers section, find tutorials and tools that will help you grow as a developer and scale your project or business, and subscribe to topics of interest.Sign up now
There is no state called “Running” in Thread.State
The way of explanation is good but as of my knowledge blocking/waiting states wont come ad thread life cycle state. It would be grate if you provide with program
- Jaya Sudhakar
Simple and clear explanation.
its a very good explanation i like your point of view because its show simple … but i think it’s better if u also give a small program to explain entire thing…but thank you somuch it is much more benfical to me for understanding lifecycle of thread…
- Dolly kumari.
Nice. Explanation is very good. But it’s still better if you explain with a small program.
Very nice explanation…
I am new to this field. I think that a thread can be (in one of) Ready or Running or waiting or delayed or blocked states only if the process/program (in which the thread is there) is currently in Ready or Running or Waiting states. In other words, If the program/process is is in hold or finished states then any thread (in that process/program) will not be in any one of the states stated above. Please clarify if I am correct.
it would be better if you explained with a small program…
- g srinivas
Mr. Pankaj Kumar, I am putting 2 years of gap of exp. can you help me about project, interview questions for exps. i read your blog. it’s nice & good. i like your language, because you have written in simple english.
- Pankaj Patil