Thread join on itself

by

The concept of a thread joining itself does not make sense.

It happens out that the join() method uses the isAlive() method to
determine when to return from the join() method. In the current implementation, it also
does not check to see if the thread is joining itself.
In other words, the join() method returns when and only when the thread is no longer alive. This will have the effect of
waiting forever.

More Related Contents:

  1. Why is i++ not atomic?
  2. Java Thread Garbage collected or not
  3. Synchronization vs Lock
  4. What is the difference between atomic / volatile / synchronized?
  5. Waiting on a list of Future
  6. How to properly shutdown java ExecutorService
  7. Why not to start a thread in the constructor? How to terminate?
  8. Prime numbers by Eratosthenes quicker sequential than concurrently?
  9. Thread Safe singleton class
  10. Why is it not a good practice to synchronize on Boolean?
  11. Java Synchronized Block for .class
  12. Synchronization of non-final field
  13. Returning value from Thread
  14. How to solve the “Double-Checked Locking is Broken” Declaration in Java?
  15. How to check if current thread is not main thread
  16. CompletableFuture is not getting executed. If I use the ExecutorService pool it works as expected but not with the common ForkJoinPool
  17. When does Java’s Thread.sleep throw InterruptedException?
  18. Difference between WAIT and BLOCKED thread states
  19. In Java critical sections, what should I synchronize on?
  20. Java’s Fork/Join vs ExecutorService – when to use which?
  21. Java: How to stop thread? [duplicate]
  22. Odd even number printing using thread
  23. Warning message “uses or overrides a deprecated API” encountered during code compilation
  24. Why single thread is faster than multithreading in Java?
  25. Run Java Threads sequentially
  26. JavaFX launch another application
  27. How to increase maximum number of JVM threads (Linux 64bit)
  28. Java Server – Multiple ports?
  29. calling thread.start() within its own constructor [duplicate]
  30. TestNG parallel Execution with DataProvider

Leave a Comment