OpenJDK for telecom
Carrier-grade Java runs the BSS and OSS stack: charging, mediation, provisioning, order management. When one of those nodes fails, a telco operator needs to reconstruct what happened, not re-run it. Eliya is an OpenJDK 25 LTS distribution that puts the evidence on disk before the failure, and keeps it inside your perimeter.
One requirement an external wrapper cannot meet
Most operational requirements in a telecommunications estate live in the configuration space: you set a flag, a Helm value, or an environment variable and you are done. The hard ones do not. Reconstructing a failed charging transaction needs the last execution profile, the heap state, and the crash log to already exist at the moment the JVM dies. That is crash-path behaviour, run by the VM itself, and no wrapper script or sidecar can guarantee the trace survives a process that is going down. It is one of several requirements that fall outside what external tooling can reach; the policy point essay sets out the general case, here applied to carrier-grade operations.
What Eliya gives a telecom workload today
One flag, -XX:EliyaProfile=Production, activates the Phase 1 operational-readiness defaults:
- Heap dump on OutOfMemoryError, written to a structured, predictable path rather than the working directory.
- A crash-log path that does not die with the container, so post-incident reconstruction has something to read.
- Native Memory Tracking (summary) and reinforced container support, which matter when mediation and charging nodes are packed into memory-limited pods.
- Exit on OutOfMemoryError, so a wedged node fails fast and the orchestrator can replace it.
Diagnostic data stays on operator infrastructure. No SaaS, no telemetry, no phone-home. For operators with data-residency obligations, the evidence never leaves the network it was generated on.
Built for the cadence telecom runs on
Eliya ships quarterly Critical Patch Updates within two weeks of each upstream OpenJDK release, on an LTS line, so a long-lived BSS platform can pin a version and still receive security maintenance. It is the same Java you already run: the upstream OpenJDK 25 source tree, GPLv2 with the Classpath Exception, no API changes, no custom JIT or GC.
Where this is going
Phase 2 adds continuous JFR and unified GC logging as defaults under the same flag, so the last day of execution profile is on disk before a failure. Compliance-aligned profile values are demand-gated and sit further out on the roadmap; they are not shipping today. The roadmap is explicit about what is built and what is not.
Telecom is also where Asymm Systems builds Dial, its build-time TMF Open Digital Architecture (ODA) conformance work, so the runtime and the ecosystem share the same compliance-conscious premise.
Next: download Eliya, read the thesis, or compare options in Choosing a JDK in 2026.
Eliya 
Dial