What does this thread join code mean?

by

What does this thread join code mean?

To quote from the Thread.join() method javadocs:

join() Waits for this thread to die.

There is a thread that is running your example code which is probably the main thread.

  1. The main thread creates and starts the t1 and t2 threads. The two threads start running in parallel.
  2. The main thread calls t1.join() to wait for the t1 thread to finish.
  3. The t1 thread completes and the t1.join() method returns in the main thread. Note that t1 could already have finished before the join() call is made in which case the join() call will return immediately.
  4. The main thread calls t2.join() to wait for the t2 thread to finish.
  5. The t2 thread completes (or it might have completed before the t1 thread did) and the t2.join() method returns in the main thread.

It is important to understand that the t1 and t2 threads have been running in parallel but the main thread that started them needs to wait for them to finish before it can continue. That’s a common pattern. Also, t1 and/or t2 could have finished before the main thread calls join() on them. If so then join() will not wait but will return immediately.

t1.join() means cause t2 to stop until t1 terminates?

No. The main thread that is calling t1.join() will stop running and wait for the t1 thread to finish. The t2 thread is running in parallel and is not affected by t1 or the t1.join() call at all.

In terms of the try/catch, the join() throws InterruptedException meaning that the main thread that is calling join() may itself be interrupted by another thread.

while (true) {

Having the joins in a while loop is a strange pattern. Typically you would do the first join and then the second join handling the InterruptedException appropriately in each case. No need to put them in a loop.

More Related Contents:

  1. StreamCorruptedException: invalid type code: AC
  2. What is a daemon thread in Java?
  3. Avoid synchronized(this) in Java?
  4. How to wait for all threads to finish, using ExecutorService?
  5. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  6. Is multi-thread output from System.out.println interleaved
  7. When and how should I use a ThreadLocal variable?
  8. Running code in main thread from another thread
  9. What is the difference between Thread.start() and Thread.run()?
  10. java thread.sleep puts swing ui to sleep too
  11. Why invoke Thread.currentThread.interrupt() in a catch InterruptException block?
  12. Why use a ReentrantLock if one can use synchronized(this)?
  13. Java Wait for thread to finish
  14. Is it safe to construct Swing/AWT widgets NOT on the Event Dispatch Thread?
  15. How to terminate a thread blocking on socket IO operation instantly?
  16. Is Java Regex Thread Safe?
  17. Instruction reordering & happens-before relationship [duplicate]
  18. running 3 threads in sequence java
  19. Are volatile variable ‘reads’ as fast as normal reads?
  20. Is the Swing repaint() method still safe to use outside the EDT in Java 7+?
  21. How to wait for all tasks in an ThreadPoolExecutor to finish without shutting down the Executor?
  22. Are Thread.sleep(0) and Thread.yield() statements equivalent?
  23. What could be the cause of RejectedExecutionException
  24. Thread join on itself
  25. Is having a single threadpool better design than multiple threadpools
  26. Why does an IllegalThreadStateException occur when Thread.start is called again
  27. What makes the execution order of threads unpredictable?
  28. Why is Thread.stop() so dangerous
  29. Updating your UI and forcibly waiting before continuing JavaFX
  30. How to test methods that call System.exit()?

Leave a Comment