Java Threads and Shutdown Hook

Question

I've just run into an interesting issue. It seems that if, in Java, a thread calls System.exit() it cannot then be joined via Thread.join().

This is causing me issues as I want to use a shutdown hook to clean up after my application, such as:

Runtime.getRuntime.addShutdownHook(new Thread() {
    public void run() {
        reader.join();
        writer.join();
        in.close();
        out.close();
    }
});

The idea is that it ensures that the threads have finished with their respective resources, before closing those resources. The problem is that there a 3 situations by which the shutdown hook can be invoked. They are:

User hits [ctrl] + [C].
Reader thread completes, and calls System.exit().
Writer thread completes, and calls System.exit().

The first case, where the user hits [ctrl] + [C] works fine. But in either of the other 2 cases, the shutdown hook blocks forever. This is a knock-on effect of the fact that one Thread.join(), which is called against a thread having already called System.exit(), blocks forever.

Thus, I have 2 questions. Firstly, I know that I could use Thread.join(long millis) instead so that they won't block indefinitely, but can anyone think of a more elegant solution? Secondly, while one can call Thread.join() against the same thread twice and on the second occasion it will simply return immediately, does anyone know of a reason why calling Thread.join() against a thread that has already called System.exit() blocks indefinitely and doesn't just return immediately?

Why not try to avoid calling System.exit() and instead arrange a proper cleanup and let the JVM exit naturally? — assylias
– assylias, Commented Jul 18, 2013 at 15:51
Also note that "If System.exit() is invoked after the virtual machine has begun its shutdown sequence then if shutdown hooks are being run this method will block indefinitely." - do you call System.exit() twice by any chance? (Reference) — assylias
– assylias, Commented Jul 18, 2013 at 15:53

Tom Hawtin - tackline · Accepted Answer · 2013-07-18 16:01:52Z

2

System.exit if successful does not return even via throwing an exception, so the thread will never complete. This wasn't an issue before shutdown hooks.

Workaround would be to usual standard locks (or even just hack it with new Thread(new Runnable() { public void run() { System.exit(0); }}).start();).

answered Jul 18, 2013 at 16:01

Tom Hawtin - tackline

148k30 gold badges222 silver badges314 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

user207421 · Accepted Answer · 2013-07-19 00:04:03Z

1

What you are doing is specifically prohibited:

Shutdown hooks should also finish their work quickly.

Joining random threads cannot be described as 'quick'.

Obviously those threads should close their own streams when they exit. If they don't exit, how will calling join() accomplish anything?

answered Jul 19, 2013 at 0:04

user207421

312k45 gold badges324 silver badges493 bronze badges

1 Comment

greydamian Over a year ago

Thanks for your reply. Apologies, to try to keep my question short and to the point, I obviously omitted quite a lot of code. I actually first call a method against the threads to tell them they should finish ASAP, before I call the Thead.join()s. Unfortunately, the threads don't have independent resources. So they can't close their own resources in case the other thread is still using them.

Joshua · Accepted Answer · 2013-07-18 15:52:53Z

0

It is not recommended to use System.exit() as that just terminates the JVM. There are other concurrency tools like a CountDownLatch. You could even use a finally to clean up correctly on shutdown.

answered Jul 18, 2013 at 15:52

Joshua

26.8k22 gold badges80 silver badges107 bronze badges

Comments

Jilles van Gurp · Accepted Answer · 2013-07-18 16:35:07Z

0

Use executors and don't use join or manually create threads.

When using an executor and the other stuff in java.util.concurrent, you can simply call shutdown and wait for it to terminate, specify a timeout, etc. Much more robust. If you are using java 1.7, use try with resources to close your streams as well. That way, you don't have much cleanup work to do beyond shutting down your executor. If not, use a finally block. Never call close anywhere else than from a finally block.

answered Jul 18, 2013 at 16:35

Jilles van Gurp

8,4225 gold badges42 silver badges48 bronze badges

Collectives™ on Stack Overflow

Java Threads and Shutdown Hook

4 Answers 4

Comments

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related