Page History

When certain kinds of errors are detected, such as irrecoverable logic errors, rather than risk data corruption by continuing to execute in an indeterminate state, the appropriate strategy may be for the system to quickly shut down, allowing the operator to start it afresh in a determinate state.
 Section 6.46, "Termination Strategy \[REU\]," \[[ISO/IEC TR 24772:2010|AA. Bibliography#ISOReferences#ISO/IEC TR 24772-2010]\] says:

{{Runtime.exit()}} is the typical way of exiting a program. According to the Java API \[[API 06|AA. Bibliography#APIReferences#API 06]\] {{Runtime.exit()}}:

{{Runtime.halt()}} is similar to {{Runtime.exit()}} but does _not_ run shutdown hooks or finalizers. According to the Java API \[[API 06|AA. Bibliography#APIReferences#API 06]\], {{Runtime.halt()}}

According to the Java API \[[API 2006|AA. Bibliography#APIReferences#API 06]\], Class {{Runtime}}, method {{addShutdownHook()}},

To avoid race conditions or deadlock between shutdown actions, it may be better to run a series of shutdown tasks from one thread by using a single shutdown hook \[[Goetz 2006|AA. Bibliography#GoetzReferences#Goetz 06]\].