Java Multithreading concept and join() method

by

You must understand , threads scheduling is controlled by thread scheduler.So, you cannot guarantee the order of execution of threads under normal circumstances.

However, you can use join() to wait for a thread to complete its work.

For example, in your case

ob1.t.join();

This statement will not return until thread t has finished running.

Try this,

class Demo {
   Thread t = new Thread(
                 new Runnable() {
                     public void run () {
                         //do something
                     }
                  }
    );
    Thread t1 = new Thread(
                 new Runnable() {
                     public void run () {
                         //do something
                     }
                  }
    );
    t.start(); // Line 15
    t.join();  // Line 16
    t1.start();
}

In the above example, your main thread is executing. When it encounters line 15, thread t is available at thread scheduler. As soon as main thread comes to line 16, it will wait for thread t to finish.

NOTE that t.join did not do anything to thread t or to thread t1. It only affected the thread that called it (i.e., the main() thread).

Edited:

t.join(); needs to be inside the try block because it throws the InterruptedException exception, otherwise you will get an error at compile time. So, it should be:

try{
    t.join();
}catch(InterruptedException e){
    // ...
}

More Related Contents:

  1. What does ‘synchronized’ mean?
  2. Avoid synchronized(this) in Java?
  3. Difference between volatile and synchronized in Java
  4. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  5. Synchronizing on String objects in Java
  6. Java synchronized method lock on object, or method?
  7. Java Synchronized Block for .class
  8. Synchronization of non-final field
  9. Happens-before relationships with volatile fields and synchronized blocks in Java – and their impact on non-volatile variables?
  10. If I synchronized two methods on the same class, can they run simultaneously?
  11. Is ConcurrentHashMap totally safe?
  12. In Java critical sections, what should I synchronize on?
  13. What is the difference between a synchronized method and synchronized block in Java? [duplicate]
  14. Should you synchronize the run method? Why or why not?
  15. Java volatile modifier and synchronized blocks
  16. Difference between Synchronized block with wait/notify and without them?
  17. Do two synchronized methods execute simultaneously
  18. If a synchronized method calls another non-synchronized method, is there a lock on the non-synchronized method
  19. Java: notify() vs. notifyAll() all over again
  20. Java synchronized static methods: lock on object or class
  21. Is java.sql.Connection thread safe?
  22. Is it legal to call the start method twice on the same Thread?
  23. Is iterating ConcurrentHashMap values thread safe?
  24. How to scale threads according to CPU cores?
  25. kill -3 to get java thread dump
  26. In Java is it possible to re-open System.in after closing it
  27. do we need volatile when implementing singleton using double-check locking
  28. In Java, how do you determine if a thread is running?
  29. Interview: How to ensure that a thread runs after another?
  30. why java security manager doesn’t forbid neither creating new Thread() nor starting it?

Leave a Comment