Walk through the thread lifecycle states — and which one signals a problem in a thread dump?
Reviewed by Gurusankar M.
Short Answer
NEW → RUNNABLE → (BLOCKED / WAITING / TIMED_WAITING) → TERMINATED. In a thread dump, lots of BLOCKED threads point to lock contention; many WAITING threads on the same monitor can indicate a missed notify or a stuck downstream call.
On this page
Concept Made Simple
Coffee Chat Question
“Walk through the thread lifecycle states — and which one signals a problem in a thread dump?”
Remember It Faster
Mind Map Answer
- RUNNABLE
- running or ready (incl. on-CPU I/O)
- BLOCKED
- waiting to acquire a monitor lock
- WAITING
- wait()/join()/park() — no timeout
- TIMED_WAITING
- sleep()/wait(ms)/await(ms)
Think Beyond the Expected
What If?
A thread dump shows dozens of threads BLOCKED on the same lock — what does that mean?
They're all queued to enter a synchronized block held by one thread. That's lock contention — the holder is slow (or stuck on I/O), serializing everyone behind it. Find the lock owner and reduce the critical section or switch to a finer-grained lock.
Real World
Reading thread states in a jstack dump is the first triage step for latency incidents: BLOCKED clusters = contention, WAITING clusters = a stalled dependency or deadlock.
Interviewer's Expectation
Keywords they're listening for:
- the 5 states
- BLOCKED = monitor contention
- WAITING vs TIMED_WAITING
- RUNNABLE includes I/O
- thread-dump reading
Common Mistakes
- Thinking RUNNABLE means actively using CPU
- Confusing BLOCKED (lock) with WAITING (wait/join)
- Ignoring thread states during incident triage
Best Practices
- Capture 2–3 thread dumps a few seconds apart
- Correlate BLOCKED threads to the lock owner
- Name threads so dumps are readable
Follow-up Questions
- Why can a thread doing socket I/O show as RUNNABLE?
- How do you find which thread holds the lock others are blocked on?
- What's the difference between BLOCKED and WAITING?
Continue Learning with AI
Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.
Plain-language foundations
I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner. Topic: Threads & Pools (Multithreading) Interview question: "Walk through the thread lifecycle states — and which one signals a problem in a thread dump?" Please: 1. Explain the core idea in simple, plain language, using an everyday analogy. 2. Define any technical terms you use. 3. Walk through one small, concrete example. 4. Finish with a single sentence I can easily remember. Keep the tone friendly and assume I'm new to this topic.
Was this answer helpful?
Affiliate links
Tools for Your Developer Workspace
Equipment for a comfortable, productive setup.
As an Amazon Associate I earn from qualifying purchases.
- MonitorView on Amazon : BenQ EW2790U 27-inch Monitor (opens in a new tab)
BenQ EW2790U 27-inch Monitor
- LaptopView on Amazon : Acer Aspire One Laptop (opens in a new tab)
Acer Aspire One Laptop
- Office ChairView on Amazon : Wakefit Gravita Ergonomic Office Chair (opens in a new tab)
Wakefit Gravita Ergonomic Office Chair