Java · Theory

Interrupting Thread

Theory

129/270

Interrupting Thread

Interrupting Thread is part of Java concurrency. A thread is a path of work inside a process. Create with Thread or Runnable, then call start() — not run(). run() only runs on the same thread.

For Interrupting Thread: if two threads share data, synchronize or the result can be wrong. sleep pauses. join waits for another thread to finish. daemon threads die when all user threads finish.

Interrupting Thread deadlock: two threads wait for each other’s lock forever. Avoid by locking in the same order. Don’t guess thread order — it can change every run.

Let's take this on the board with one tiny Main class — no extra files. Interrupting Thread — start() schedules the thread; main also prints — order may vary. Start from main, go line by line, and stop at each print. That output is the proof for Interrupting Thread.

Exam tip

start() vs run() is a classic interview question.

Example

// Thread demo
public class Main {
  public static void main(String[] args) {
    Thread t = new Thread(() -> System.out.println("Hi from thread"));
    t.start();
    System.out.println("Hi from main");
  }
}

Interrupting Thread — start() schedules the thread; main also prints — order may vary.

Short notes

DefInterrupting Thread — thread = one path of work. start() schedules it. run() does not.
RuleInterrupting Thread — shared data needs synchronization.
RememberInterrupting Thread — sleep = pause. join = wait for other thread.
TrapInterrupting Thread — calling run() instead of start(). Deadlock = locks in wrong order.

// Thread demo public class Main { public static void main(String[] args) { Thread t = new Thread(() -> System.out.println("Hi from thread")); t.start(); System.out.println("Hi from main"); } }

Interrupting Thread

Example

Short notes

Questions

Interrupting Thread

Example

Short notes

Questions