Issue Summary

Confluence’s built‑in “Java Version and Vendor” health check currently reports a Critical failure when the Java runtime string does not exactly match a small allow‑list (Java(TM) SE Runtime Environment, OpenJDK Runtime Environment). This behavior is stricter than our current Supported Platforms stance on OpenJDK distributions and results in alarming but non‑critical health check failures for customers running supported OpenJDK distributions such as Azul Zing. We would like to lower the severity from Critical to Warning and update the wording to better reflect the documented support policy.

Steps to Reproduce

1. Install and run Confluence Data Center on an OpenJDK distribution whose java -version output uses a different Java runtime name than:
   • Java(TM) SE Runtime Environment, or
   • OpenJDK Runtime Environment
     Example (Azul Zing 17):

     • $ java -version
       java version "17.0.10.0.101" 2024-04-12 LTS
       Java Runtime Environment Zing24.02.100.0+5 (build 17.0.10.0.101+3-LTS)
       Zing 64-Bit Tiered VM Zing24.02.100.0+5 (build 17.0.10.0.101-zing_24.02.100.0-b5-product-linux-X86_64, mixed mode)
       

2. Start Confluence and navigate to:
   Administration → Troubleshooting and Support Tools → Health Checks.
3. Observe the “Java Version and Vendor” health check status.
4. Review the application logs for the JDK health check result.

Expected Results

• The “Java Version and Vendor” health check should:
  • Report a Warning (non‑critical) status when Confluence is running on a non‑Temurin/OpenJDK OpenJDK distribution (e.g. Zing), and
  • Display wording that:
    • Acknowledges that Atlassian supports OpenJDK distributions in general.
    • Clarifies that Atlassian primarily tests with Temurin.
    • Explains that if a problem is ultimately caused by the Java distribution itself, the customer may need to work with their Java vendor, as per the Supported Platforms documentation:
      • [Supported Platforms | Confluence Data Center 10.2 | Atlassian Documentation|https://confluence.atlassian.com/doc/supported-platforms-207488198.html]

• The health check severity should be aligned with this nuanced support stance and not suggest that the platform is fundamentally unsupported or unsafe.

Actual Results

• The “Java Version and Vendor” health check currently fails with Critical severity when the Java runtime string does not exactly match the small allowed list (e.g. when using Azul Zing).

• This is more alarming than warranted given our current documentation and creates inconsistency with other products (Jira/Bitbucket) that do not yet have a similar check.

The below exception / log entry is thrown in the Confluence log file

• 2026-01-30 10:41:57,700 ERROR [Caesium-1-2]
  [troubleshooting.healthcheck.concurrent.SupportHealthCheckProcess] lambda$getCompletedStatuses$0
  Health check 'Java Version and Vendor' failed with severity 'critical':
  'Java Runtime Environment is not a supported Java distribution.'
  

Workaround

Currently there is no known product‑level configuration to change the health check severity or message from within the UI.