Question

In this code example, the ExecutorService is used one and allowed to go out of scope.

public static void main(String[] args)
{
    ExecutorService executorService = Executors.newFixedThreadPool(3);
    executorService.submit(new Runnable()
    {
        public void run()
        {
            System.out.println("hello");
        }
    });
}

Once executorService is out of scope, it should get collected and finalized. The finalize() method in ThreadPoolExecutor calls shutdown().

/**
 * Invokes {@code shutdown} when this executor is no longer
 * referenced and it has no threads.
 */
protected void finalize() {
    shutdown();
}

Once shutdown() is called, the pool threads should terminate and the JVM should be allowed to exit. However the executorSerivce is never getting collected and thus the JVM stays alive. Even calls to System.gc() don’t seem to work. Why isn’t executorService getting collected even after main() terminates?

Note: I know I should call shutdown() myself and I always do outside of testing. I’m curious why finalization isn’t working as a back-up here.

Answer 1

This doesn’t really have anything to do with GC being non-deterministic, although it doesn’t help! (That is one cause in your example, but even if we ‘fixed’ it to eat up memory and force a collection, it still wouldn’t finalize)

The Worker threads that the executor creates are inner classes that have a reference back to the executor itself. (They need it to be able to see the queue, runstate, etc!) Running threads are not garbage collected, so with each Thread in the pool having that reference, they will keep the executor alive until all threads are dead. If you don’t manually do something to stop the threads, they will keep running forever and your JVM will never shut down.