0 views collected around this technical thread.
This article explains how to achieve graceful shutdown for Java applications by using Linux kill signals, JVM SignalHandler registration, Runtime.addShutdownHook, and Spring Boot's actuator shutdown endpoint, providing code examples and configuration details for safe resource cleanup.
This article explains how to use the Linux kill command with SIGTERM, SIGQUIT, SIGKILL, and SIGSTOP signals to gracefully terminate, debug, force‑stop, or pause processes while minimizing data loss and providing practical command examples.
This article examines how session IDs are derived for the kill command in OceanBase, compares IDs obtained through show processlist, information_schema.processlist, and oceanbase.__all_virtual_processlist, and demonstrates methods to terminate all connections of a specific tenant across different observers and obproxies.
This article explains why using the Linux kill -9 command to stop Java services can cause data loss, demonstrates the differences between forceful and graceful termination, and provides multiple Spring Boot shutdown solutions—including kill -15, actuator endpoints, custom Tomcat connectors, and @PreDestroy hooks—complete with code examples.
This article explains how the Linux kill -9 command can cause data loss and service instability, demonstrates safer alternatives such as kill -15 and Spring Boot's built‑in shutdown mechanisms, and provides code examples for implementing graceful termination, custom shutdown hooks, and pre‑destroy data backup in Java backend services.