Graceful Shutdown in Java: Using Shutdown Hooks and ThreadPool Management

Graceful shutdown means that before a service is stopped, it performs cleanup operations such as closing threads and releasing resources instead of terminating abruptly.

In Java, you can register a shutdown hook using Runtime.getRuntime().addShutdownHook() to ensure the program exits smoothly; other languages have similar mechanisms.

Below is a full example that creates a cached thread pool, submits several tasks, and registers two shutdown hooks to wait for task completion, shut down the executor, and log the shutdown process.

public
class
ShutdownGraceFullTest
{
/**
* 使用线程池处理任务
*/
public
static
ExecutorService
executorService =
Executors
.newCachedThreadPool();
}

The program prints timestamps showing each thread’s start and finish, confirming that tasks complete before the JVM exits.

To trigger a graceful shutdown, send a SIGTERM signal (e.g., kill -15 <pid> ). The JVM then runs the registered shutdown hooks, where you can close sockets, clean temporary files, notify subscribers, and release other resources.

In contrast, using kill -9 <pid> forces an immediate termination without any chance for cleanup, effectively a hard crash.

For thread‑pool shutdown, call executorService.shutdown() followed by executorService.awaitTermination(1500, TimeUnit.SECONDS) to wait for running tasks. shutdownNow() attempts to interrupt running tasks and stops accepting new ones, but it does not guarantee immediate termination.

Note that the JVM may invoke multiple shutdown hooks in an unspecified order; all must finish before the JVM exits. If a hook performs blocking operations, the JVM will wait, which explains why some applications appear to hang after receiving SIGTERM.