Open-source JVM diagnostics

JVM Breakglass

Controlled live inspection for JVM applications.

A Matlux Java/Clojure library that embeds a local nREPL endpoint inside an application, so experienced engineers can inspect registered objects, Spring beans, and diagnostic expressions from the running JVM.

JVM Breakglass emergency cabinet banner showing a REPL, JVM runtime, and coffee cup

What It Enables

JVM Breakglass is for controlled engineering situations where ordinary logs, metrics, and dashboards do not answer the question quickly enough. The host application integrates the library first; it is not an external attach-to-any-JVM product.

01

Inspect registered live objects

Expose selected objects to the embedded REPL and inspect their fields, methods, and current runtime state.

02

Explore Spring beans

Use the Spring integration to resolve application beans and inspect the objects behind a running service.

03

Evaluate diagnostic expressions

Run Clojure expressions inside the JVM process for targeted investigation by trusted engineers.

04

Control access through JMX

Keep the listener stopped by default, then start, stop, and inspect it through the JVM management surface.

Backend engineering

Why It Matters

  • Useful when a live backend problem depends on runtime state that is hard to reproduce outside the process.
  • Gives senior engineers a controlled inspection path for Java, Clojure, and Spring services.
  • Keeps the diagnostic surface explicit: applications choose when to include it and what objects to register.
  • Demonstrates Matlux experience with JVM internals, backend troubleshooting, and pragmatic operational tooling.

Technical Shape

The library is intentionally small and direct. It sits inside the application, exposes a loopback-only nREPL listener, and provides helper namespaces for inspecting Java objects and Spring beans.

Runtime integration

Java applications can instantiate NreplServer directly; Spring applications can wire NreplServerSpring as a bean.

Local REPL endpoint

The nREPL listener binds to 127.0.0.1 and can be reached locally or through an explicit SSH tunnel.

JMX lifecycle

A management bean exposes port, started state, start, and stop operations for operational control.

Current release

Version 0.1.0 is published on Clojars with a Java 8 baseline and tests covering socket, Spring, and JMX flows across modern JDKs.

Integration

Integration Snapshot

The Maven coordinate is deliberately simple. A typical integration decides whether the listener starts automatically, which objects are exposed, and how the JMX controls fit into the operating model.

<dependency>
  <groupId>net.matlux</groupId>
  <artifactId>jvm-breakglass</artifactId>
  <version>0.1.0</version>
</dependency>

Because the REPL executes with application privileges and has no built-in authentication, it should only be enabled deliberately, kept local or tunnelled, and never exposed publicly.

Use cases

Suitable Use Cases

Backend incident investigation JVM and Spring state inspection Controlled production-support tooling Legacy Java/Clojure system diagnostics Custom observability and troubleshooting workflows

Project Resources

Prototype and tooling framing

Operational Framing

JVM Breakglass is an open-source diagnostic library, not a hosted SaaS platform or generic monitoring product. It is powerful because it runs inside the application process, which means it must be handled as privileged engineering tooling with clear access controls and operating procedures.

Need a controlled way to inspect a complex JVM system?

Matlux can help design the integration, operational guardrails, and backend troubleshooting workflow around this kind of live diagnostic capability.