| How is it priced? | Per employee across the whole organization, including staff of contractors and outsourcers who support internal operations, whether or not they use Java (Oracle price list, 8 October 2026). Oracle sets the numbers and AceMQ does not reprint them. | Set by each vendor, often by server or core rather than headcount. Ask each vendor for a quote for your estate. | No license fee for the JDK. AceMQ support is a separate contract, quoted on request. |
|---|
| Where do security updates come from? | Oracle, while the subscription runs and the release is in Premier or Extended Support. | The vendor, on its own published schedule for each LTS release. | The publisher of the build: the Eclipse Adoptium project for Temurin, Amazon for Corretto, Microsoft for its build, each on its own published dates. AceMQ produces no JDK patches. |
|---|
| Who answers when the JVM crashes at 3am? | Oracle Support, through a service request, for the Oracle JDK builds the subscription covers. | The vendor, for defects in its own build. | An AceMQ engineer 24/7, with response targets from 15 minutes, by plan, for diagnosis and operations. A defect that needs a JDK code fix goes to the OpenJDK project or the build vendor, because AceMQ does not patch the JDK. |
|---|
| What do you have to change? | Nothing. This is the option that needs no migration. | Replace the JDK in images and installers with the vendor's build, then test TLS, truststores and default settings. | The same replacement, plus an update routine you own. AceMQ writes the plan and the standard stays with your team. |
|---|
| How long can you stay on Java 8? | Extended Support to December 2030, per Oracle's support roadmap. | Azul lists Java 8 production support to December 2030. Red Hat's full support for OpenJDK 8 ends on 30 November 2026 and optional paid Extended Life Cycle Support (ELS-1) runs to 31 December 2032. | Eclipse Temurin 8 is supported at least until December 2030. Amazon Corretto 8 reaches end of life in December 2030. |
|---|
| When does it fit? | You want one vendor accountable for the JDK and you accept per-employee pricing. | You want a vendor to stand behind the JDK with an SLA, and you want to leave Oracle. | Your team applies updates routinely, runs on Kubernetes or a cloud that publishes its own build, and wants senior engineers on call rather than a second JDK contract. |
|---|