How to shutdown an ExecutorService?

by

The typical pattern is:

executorService.shutdownNow();
executorService.awaitTermination();

When calling shutdownNow, the executor will (generally) try to interrupt the threads that it manages. To make the shutdown graceful, you need to catch the interrupted exception in the threads or check the interrupted status. If you don’t your threads will run forever and your executor will never be able to shutdown. This is because the interruption of threads in Java is a collaborative process (i.e. the interrupted code must do something when asked to stop, not the interrupting code).

For example, the following code prints Exiting normally.... But if you comment out the line if (Thread.currentThread().isInterrupted()) break;, it will print Still waiting... because the threads within the executor are still running.

public static void main(String args[]) throws InterruptedException {
    ExecutorService executor = Executors.newFixedThreadPool(1);
    executor.submit(new Runnable() {

        @Override
        public void run() {
            while (true) {
                if (Thread.currentThread().isInterrupted()) break;
            }
        }
    });

    executor.shutdownNow();
    if (!executor.awaitTermination(100, TimeUnit.MICROSECONDS)) {
        System.out.println("Still waiting...");
        System.exit(0);
    }
    System.out.println("Exiting normally...");
}

Alternatively, it could be written with an InterruptedException like this:

public static void main(String args[]) throws InterruptedException {
    ExecutorService executor = Executors.newFixedThreadPool(1);
    executor.submit(new Runnable() {

        @Override
        public void run() {
            try {
                while (true) {Thread.sleep(10);}
            } catch (InterruptedException e) {
                //ok let's get out of here
            }
        }
    });

    executor.shutdownNow();
    if (!executor.awaitTermination(100, TimeUnit.MICROSECONDS)) {
        System.out.println("Still waiting...");
        System.exit(0);
    }
    System.out.println("Exiting normally...");
}

More Related Contents:

  1. How to properly shutdown java ExecutorService
  2. How to wait for all threads to finish, using ExecutorService?
  3. ExecutorService, how to wait for all tasks to finish
  4. ExecutorService that interrupts tasks after a timeout
  5. Handling exceptions from Java ExecutorService tasks
  6. Executors.newCachedThreadPool() versus Executors.newFixedThreadPool()
  7. Choose between ExecutorService’s submit and ExecutorService’s execute
  8. How to properly use Java Executor?
  9. What are the advantages of using an ExecutorService?
  10. Java’s Fork/Join vs ExecutorService – when to use which?
  11. Turning an ExecutorService to daemon in Java
  12. Is ExecutorService (specifically ThreadPoolExecutor) thread safe?
  13. Impossible to make a cached thread pool with a size limit?
  14. ThreadPoolExecutor Block When Queue Is Full?
  15. Java ExecutorService: awaitTermination of all recursively created tasks
  16. How to use invokeAll() to let all thread pool do their task?
  17. FixedThreadPool vs CachedThreadPool: the lesser of two evils
  18. ThreadPoolExecutor Block When its Queue Is Full?
  19. How to stop all runnable thread in java executor class?
  20. ExecutorService vs Casual Thread Spawner
  21. How to pause/resume all threads in an ExecutorService in Java?
  22. Java Executors: how can I stop submitted tasks?
  23. Removing all queued tasks of an ThreadPoolExecutor
  24. Shutdown ExecutorService gracefully in webapp?
  25. Dynamic Thread Pool
  26. ExecutorCompletionService? Why do need one if we have invokeAll?
  27. java.lang.OutOfMemoryError: Java heap space
  28. Is it safe to get values from a java.util.HashMap from multiple threads (no modification)?
  29. Throttling javafx gui updates
  30. LinkedBlockingQueue vs ConcurrentLinkedQueue

Leave a Comment