Troubleshooting

The asymm CLI

Eliya ships a small diagnostic helper at $JAVA_HOME/bin/asymm. Use it to confirm which runtime you're on and to print build metadata.

Output includes JDK version, vendor, build date, platform, and which Eliya features are active. Attach this output to any issue you file on GitHub.

Common issues

TLS handshake fails with "protocol disabled" or "no cipher suites in common"

Eliya disables SSLv3, TLS 1.0, TLS 1.1, and weak cipher suites by default. A legacy peer insisting on these will fail to negotiate. Either upgrade the peer (correct fix) or opt out of hardening for this JVM invocation:

"Unrecognized VM option 'UseEliyaDefaults'"

You're running a non-Eliya JVM. Confirm with java -version — the version string must include "Eliya". If not, check JAVA_HOME, your PATH, and SDKman's current version (sdk current java).

SHA256SUMS.txt verification fails

Re-download both the archive and the SHA256SUMS.txt from the same GitHub Release page. If the re-download still fails, do not run the archive — report to security@asymm.systems.

GC pauses exceed 50 ms despite -XX:+UseEliyaDefaults

The 50 ms target is aspirational — G1 can exceed it under heavy allocation pressure, large live sets, or tight heap sizing. Diagnose with:

Usual fixes: larger heap (-Xmx), profile allocation hot spots, or swap to Shenandoah or ZGC for sub-10 ms pauses at the cost of throughput.

SDKman says version not found

Run sdk update to refresh the candidate metadata. If still not found 24 hours after a new Eliya release, check the releases page and file an issue.

Eliya runs but applications behave differently than on Corretto/Zulu

The most likely cause is the hardened java.security — check TLS negotiation and cipher suite selection. Second most likely: -XX:+UseEliyaDefaults is set and G1 tuning is interacting with your allocation profile differently from the default 200 ms target. See the migration guide for behavioural parity details.

Filing an issue

Non-security issues: open a GitHub issue on asymmsystems/eliya-jdk. Include:

• asymm --info output
• java -version
• OS, architecture, container image if applicable
• Full command line (flags, JAR path)
• Minimal reproducer if possible

Security issues: email security@asymm.systems — see the security page.