[Bug] FullNode.jar rejects Java 17 on amd64 architecture

[NabiKAZ]

Bug Description

FullNode.jar from the official release rejects Java 17 on x86_64 architecture with the error:

Java 1.8 is required for amd64 architecture. Detected version 17

According to the current java-tron documentation, JDK 8 or JDK 17 should be supported. However, the released FullNode binary appears to have a hard check that prevents running on Java 17.

The downloaded JAR was verified against the official SHA256 checksum.

Environment

Network
Mainnet

Software Versions
OS: Ubuntu 24.04 LTS (WSL2)
JVM: OpenJDK 17.0.19 amd64
Git Commit: N/A (official release JAR)
Version: GreatVoyage-v4.7.3.1 (Pyrrho)
Code: N/A

JAR Information

File: FullNode.jar
SHA256:
cae166bf9c980ebe16f8d0eea9381d80e2b7311a192d740942e90f5b88d9d424

Architecture:
uname -m output:
x86_64
Java version:
java --version output:
openjdk 17.0.19 2026-04-21
OpenJDK Runtime Environment (build 17.0.19+10-1-24.04.2-Ubuntu)
OpenJDK 64-Bit Server VM (build 17.0.19+10-1-24.04.2-Ubuntu, mixed mode, sharing)

Configuration

Running a standard FullNode configuration:
FullNode.jar -c config.conf
No custom code changes were made.

Expected Behavior

The FullNode should start successfully with Java 17 because JDK 17 is documented as supported for x86_64 systems.
Expected behavior:
Node starts normally and begins loading configuration and database.

Actual Behavior

The application exits immediately with:
Java 1.8 is required for amd64 architecture. Detected version 17
The error happens before loading the configuration file.

Frequency

• Always (100%)
• Frequently (>50%)
• Sometimes (10-50%)
• Rarely (<10%)

Steps to Reproduce

1. Install Java 17 on Ubuntu 24.04 x86_64.
2. Verify Java version:
   java --version
   Output:
   openjdk 17.0.19
3. Download the official FullNode.jar release.
4. Run:
   java -Xmx24g -Xms24g -jar FullNode.jar -c config.conf
5. The following error appears:
   Java 1.8 is required for amd64 architecture. Detected version 17

Logs and Error Messages

Java 1.8 is required for amd64 architecture. Detected version 17

Additional Context (Optional)

The same binary runs with Java 8:
openjdk version "1.8.0_492"
OpenJDK 64-Bit Server VM
but fails with Java 17.

The issue seems to be related to the Java version detection logic inside the released JAR. The validation check may be outdated or inconsistent with the current documentation.

Possible Solution
Update the Java version validation logic to allow Java 17 for amd64 architecture, or update the documentation if Java 17 is not actually supported.

[abn2357]

Hello, @NabiKAZ
Currently, a java-tron node supports running on both x86_64 and arm64 architectures(support for the arm64 architecture starts from version 4.8.1). JDK support varies by architecture:

• For the x86_64 architecture, currently only JDK 8 (latest minor version recommended) is supported.
• For the arm64 architecture, currently only JDK 17 is supported.

For detail information, please refer to official deploying doc.

amd64 is x86_64. Please use jdk 8 for your machine.

By the way, where did you see the statement that both JDK 8 and JDK 17 are supported across two architectures without distinction?

[halibobo1205]

Thanks for the detailed report.

This is expected behavior rather than a bug in the check itself — but the documentation is genuinely misleading, so the issue is valid and we'll fix the wording.

Current requirement. The JDK version is bound to CPU architecture, and the two are mutually exclusive — not a choice between two supported versions:

CPU Architecture	Required JDK
x86_64 / amd64	JDK 8 only
ARM64 / aarch64	JDK 17 only

This is enforced at node startup in Arch.throwIfUnsupportedJavaVersion() and mirrored at build time in build.gradle. So on your x86_64 host, JDK 8 is currently the only supported runtime — which matches what you already observed.

Going forward. JDK 17 support on x86_64 is planned for a future release. Until that lands, the constraint above stands, and the README will be updated to state the architecture-to-JDK mapping explicitly instead of the current "version 8 or 17 … based on your CPU architecture" phrasing, which reads as an either/or.

Re-labeling this as a documentation issue.

[NabiKAZ]

By the way, where did you see the statement that both JDK 8 and JDK 17 are supported across two architectures without distinction?

Thanks for your explanation and the other friend above.

I saw something written about Java 17 here:
https://developers.tron.network/docs/node-operations-issues#3-jvm-heap-and-gc

And of course, it was probably mostly AI's fault that it insisted on solving the problem and running with 17 and never said it had to be 8 ((: