jvmkill
A JVMTI agent that forcibly terminates the JVM when it cannot allocate memory or create threads.
What is jvmkill?
jvmkill is a JVMTI agent that forcibly terminates the Java Virtual Machine when it exhausts critical resources like memory or thread allocation capacity. It solves the problem of JVM instability following `OutOfMemoryError` or thread creation failures by ensuring a clean exit, allowing external process managers to restart the application.
Java developers and system administrators running long-lived JVM applications in production environments where reliability and automatic recovery are critical.
Developers choose jvmkill because it provides a more reliable alternative to native JVM options, covering both memory and thread allocation failures while remaining compatible with heap dump diagnostics for post-mortem analysis.
Overview
Terminate the JVM when resources are exhausted
Use Cases
Best For
- Preventing JVM instability after OutOfMemoryError in production
- Ensuring clean restarts for containerized Java applications
- Handling thread creation failures that native JVM options ignore
- Combining heap dump generation with forced termination
- Improving reliability in memory-constrained environments
- Automating recovery in process-managed deployments like systemd or Kubernetes
Not Ideal For
- Development environments where debugging memory leaks requires inspecting the JVM state after an OutOfMemoryError
- Applications with custom error handling or graceful degradation strategies for resource exhaustion
- Systems using Java 8u92+ where only OutOfMemoryError is a concern and thread creation failures are negligible
- Projects prioritizing minimal setup and avoiding external JVMTI agent dependencies
Pros & Cons
Pros
Immediately kills the JVM upon OutOfMemoryError or thread creation failure, preventing inconsistent states as described in the README's overview.
Compatible with -XX:+HeapDumpOnOutOfMemoryError, allowing diagnostic heap dumps before termination, per the README's notes on heap dump compatibility.
Addresses thread allocation failures that native JVM options like -XX:ExitOnOutOfMemoryError do not handle, based on the alternatives section.
Easily integrated via JVM arguments or environment variables without significant overhead, as shown in the usage instructions.
Cons
Forcibly terminates the JVM without allowing application-level recovery or cleanup, which might not suit systems needing controlled degradation.
Needs to be built with a specific JDK and integrated into JVM startup, adding deployment complexity compared to built-in options, as indicated in the building section.
Beyond enabling heap dumps, it doesn't provide additional logging or metrics to diagnose failure root causes, relying solely on termination.
Frequently Asked Questions
Related Projects
HotswapAgentJava unlimited redefinition of classes at runtime.
DripFast JVM launching without the hassle of persistent JVMs.
CapsuleDead-Simple Packaging and Deployment for JVM Apps
CRaSHThe shell for the Java Platform
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.