Upgrade to JDK 17 for ARM Architecture #5976

Activity

1. halibobo1205

   added

   type:feature

   on Aug 28, 2024
2. tronprotocol

   deleted a comment from on Aug 28, 2024
3. CarlChaoCarl commented on Aug 28, 2024

   

   CarlChaoCarl

   on Aug 28, 2024

   Contributor

   More actions

   @halibobo1205

   As far as I know
   For besu, Java 21 or later is required to build Besu
   Will java-tron limit the java version, or is it still compatible with java8
4. tronprotocol

   deleted a comment from on Aug 28, 2024
5. abn2357 commented on Aug 28, 2024

   

   abn2357

   on Aug 28, 2024

   Contributor

   More actions

   When do you plan to begin this upgrade?JDK 8 is unable to keep up with the times.
6. thuthu24 commented on Aug 28, 2024

   

   thuthu24

   on Aug 28, 2024

   More actions

   Background

   Java-Tron currently only supports Oracle JDK 8. However, despite the wide usage of JDK 8, it is no longer the most preferable option for development for multiple reasons and limitations. For instance, the End of Public Updates process for legacy releases and the End of Commercial Use under the Oracle Technology Network License Agreement for Java SE both hold that. On the contrary, JDK 17 is the LTS (Long Term Support) version of Oracle announced for free commercial use in 2021. It has significant improvements in performance, stability, and security, with advantages as follows:

   • Free Java License: Free Use License for All Users.

   [!CAUTION]
   Oracle JDK Development Kit 17.0.12 is the last planned update of JDK 17 under the NFTC. Updates after September 2024 will be licensed under the Java SE OTN License (OTN) and production use beyond the limited free grants of the OTN license will require a fee. I suggest moving to OpenJDK 17, see more distributions.

   • Java SE Universal Subscription Datasheet
   • Oracle Java SE Universal Subscription FAQ
   • Oracle Java SE Subscription Global Price List

   • LTS: Long-Term-Support, Premier Support Until September 2026 or later.
   • AArch64 Port

   [!IMPORTANT]

   • JEP 237: Linux/AArch64 Port(Release 9)
   • JEP 388: Windows/AArch64 Port(Release 16)
   • JEP 391: macOS/AArch64 Port(Release 17)

   • Garbage Collectors

   [!IMPORTANT]

   • Shenandoah JEP 379: Shenandoah: A Low-Pause-Time Garbage Collector (Production)(Release 15)
   • ZGC JEP 377: ZGC: A Scalable Low-Latency Garbage Collector (Production)(Release 15)

   • Language

   [!IMPORTANT]

   • JEP 306: Restore Always-Strict Floating-Point Semantics(Release 17)
   • JEP 409: Sealed Classes(Release 17)
   • JEP 361: Switch Expressions(Release 14)

   Related Issues and PRs

   • Expand ARM Architecture Compatibility #5954
   • Node not syncing post mandatory upgrade #5807
   • fix(readme): update description of JDK 1.8 version in use #5338
   • A fatal error has been detected by the Java Runtime Environment #4746
   • Debian, openjdk, javax.annotation.Generated cannot find symbol #4498
   • Node sync not happening at all #4472
   • Full node sync failed - Peer stats: all 0, active 0, passive 0 #4524
   • OpenJDK, newer Java versions #4211
   • Run java-tron using OpenJDK #4133
   • * What went wrong: Could not initialize class org.codehaus.groovy.runtime.InvokerHelper #3897
   • Syncing Issue #3604
   • Upgrade to JDK 11 #3542
   • Upgrade to JDK 11 #3540
   • 🚀 A series of performance improvement plans #3528
   • Can't Connect to Any Peer #3514
   • GreatVoyage-v4.1.1 java error on Ubuntu 20.04.1 LTS (Focal Fossa) #3504
   • Error creating bean with name 'blockMsgHandler': Injection of autowired dependencies failed #2379
   • Failed to deploy #2311
   • Oracle Java (JDK) 8 Installer PPA (DISCONTINUED) #2164
   • Error when running full node. Exception encountered during context initialization - cancelling refresh attempt #1179
   • Odyssey-v2.0.5 compile Error #1105
   • Added info under Prepared dependencies section, to suggest Linux Ubuntu's users, using Oracle JDK 8, instead of OpenJDK 8, to avoid error build #339
   • Java 10? - currently unable to compile java-tron with JDK 10 #295

   Scope of Impact

   • Build and deployment processes
   • Core application codes
   • Third-party dependencies
   • Development and testing environments
7. halibobo1205 commented on Aug 29, 2024

   

   halibobo1205

   on Aug 29, 2024

   CollaboratorAuthor

   More actions

   Java 21 or later is required to build

   @CarlChaoCarl Java 17 or later is required to build Java-Tron.
8. halibobo1205 commented on Aug 29, 2024

   

   halibobo1205

   on Aug 29, 2024

   CollaboratorAuthor

   More actions

   When do you plan to begin this upgrade?JDK 8 is unable to keep up with the times.

   @abn2357 The current phase is under discussion, and the evaluation will be based on the workload.
9. halibobo1205 commented on Sep 3, 2024

   

   halibobo1205

   on Sep 3, 2024

   CollaboratorAuthor

   More actions

   Try to work with both JDK8 and JDK17.
10. halibobo1205 commented on Sep 3, 2024

    

    halibobo1205

    on Sep 3, 2024

    Last edited by halibobo1205

    CollaboratorAuthor

    More actions

    Here are some common considerations:

    Caution

    1. Floating-point arithmetic
       Jdk17 may have subtle differences in floating-point precision and behavior.
       Comprehensive testing is necessary for applications that rely on precise floating-point calculations.

    • Math.pow different result

    Important

    2. Default Behavior Changes

    • JEP 358: Helpful NullPointerExceptions: Provides more detailed information for NullPointerExceptions(JDK 14+)
    • JSR 376: Java Platform Module System: Introduces the Java Module System(JDK 9+)
    • Default Garbage Collector: JDK 8: Uses Parallel GC by default, JDK 17: Uses G1 GC by default
    • ... ...

    Important

    3. JVM options Changes

    • log JVM options
    • Garbage options
    • ... ...

    Important

    4. Third-party dependencies
    Ensure all third-party libraries and dependencies support JDK17.
    Some incompatible dependencies may need to be updated or replaced.

    • springframework
    • lombok
    • javax
    • mockito
    • ... ...

    Important

    5. Gradle plugins
    Ensure all Gradle plugins support JDK17.
    Some incompatible plugins may need to be updated or replaced.

    • jacoco
    • checkstyle
    • ... ...

    Important

    6. Build and deployment process:

    • Update build scripts to support JDK17.
    • Ensure CI/CD pipelines can be built and tested in JDK17 environments.
    • Docker support

    Important

    7. Cross-JDK testing

    • Establish comprehensive test suites to ensure the functionality works correctly on JDK.
    • Conduct performance benchmarking to compare JKD8 and JDK17 performance differences.
11. Murphytron commented on Sep 3, 2024

    

    Murphytron

    on Sep 3, 2024

    More actions

    This issue has been added to the core devs community call #23, welcome to share the latest progress @halibobo1205, and discuss together with @CarlChaoCarl @abn2357 @thuthu24.
12. halibobo1205 commented on Sep 4, 2024

    

    halibobo1205

    on Sep 4, 2024

    CollaboratorAuthor

    More actions

    Caution

    8. Strong data consistency and finality
    Final data consistency is required for blockchain, and the world state usually guarantees it. Unfortunately, Java-Tron doesn't have a world state.
    We need to think about how to ensure final data consistency.
13. halibobo1205 commented on Sep 4, 2024

    

    halibobo1205

    on Sep 4, 2024

    CollaboratorAuthor

    More actions

    Caution

    1. Floating-point arithmetic
       Jdk17 may have subtle differences in floating-point precision and behavior.
       Comprehensive testing is necessary for applications that rely on precise floating-point calculations.

    • Math.pow different result : Tron Should Use StrictMath to Avoid Cross-JDK Consistency Issues. To ensure Cross-JDK compatibility for Java-Tron, I suggest a new proposal to convert Mathto StrictMath, just like for cross-platform compatibility
14. halibobo1205 commented on Sep 5, 2024

    

    halibobo1205

    on Sep 5, 2024

    CollaboratorAuthor

    More actions

    Important

    Commercial Use
    under the Java SE OTN License (OTN), only free for:
    ( i) Personal Use,
    (ii) Development Use,
    (iii) Oracle Approved Product Use, and/or
    (iv) Oracle Cloud Infrastructure Use.

    Tron's other behavior should be identified as Commercial Use.
15. halibobo1205 commented on Sep 5, 2024

    

    halibobo1205

    on Sep 5, 2024

    CollaboratorAuthor

    More actions

    Important

    JDK version compatibility

    • Java 17 or later is required to build Java-Tron？
    • Compatible with JDK8 and JDK17+?
16. 7 remaining items

    Load more
17. halibobo1205

    moved this from In progress to Todo in java-tronon Apr 22, 2025
18. halibobo1205

    moved this from Todo to In progress in java-tronon Apr 22, 2025
19. halibobo1205 commented on May 12, 2025

    

    halibobo1205

    on May 12, 2025

    Last edited by halibobo1205

    CollaboratorAuthor

    More actions

    JDK 9-17 release checklist

    • RELEASE NOTES: JDK 9

      1. JEP 223: New Version-String Scheme
      2. JEP 277: Enhanced Deprecation

    • RELEASE NOTES: JDK 10

      1. JEP 286: Local-Variable Type Inference

    • RELEASE NOTES: JDK 11

      1. JEP 320: Remove the Java EE and CORBA Modules

    • RELEASE NOTES: JDK 12

      1. JDK-8176425: Add radix indication in NumberFormatException message for Integer.decode

    • RELEASE NOTES: JDK 13

      1. JDK-8210583: Base64.Encoder and Base64.Decoder Methods Can Throw OutOfMemoryError
      2. JDK-8218228: StringBuffer(CharSequence) and StringBuilder(CharSequence) Throw NegativeArraySizeException for Negatively Sized Argument
      3. JDK-8223773: DateTimeFormatter now throws DateTimeParseException on Invalid HOUR_OF_AMPM
      4. JDK-8216558: Lookup.unreflectSetter(Field) Now Throws IllegalAccessException for Static Final Fields

    • RELEASE NOTES: JDK 14

      1. JEP 358: Helpful NullPointerExceptions
      2. JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector
      3. JDK-8233141: DatagramSocket.send and MulticastSocket.send Throw IllegalArgumentException When Socket Is Not Connected and Packet Doesn't Contain Address
      4. JDK-8233307: MulticastSocket getOption(IP_MULTICAST_IF) Returns null when outgoing interface not set
      5. JDK-8231196: DelegationPermission Allows Creating an Instance That Thows NPE on ::equals Call

    • RELEASE NOTES: JDK 15

      1. JEP 377: ZGC: A Scalable Low-Latency Garbage Collector (Production)
      2. JDK-8237890: DatagramPacket.getPort() Returns 0 When the Port Is Not Set

    • RELEASE NOTES: JDK 16

      1. JEP 396: Strongly Encapsulate JDK Internals by Default

    • RELEASE NOTES: JDK 17

      1. JEP 306: Restore Always-Strict Floating-Point Semantics
      2. JEP 391: macOS/AArch64 Port
20. halibobo1205 commented on May 16, 2025

    

    halibobo1205

    on May 16, 2025

    CollaboratorAuthor

    More actions

    Traced by #5954
21. kuny0707

    added

    v4.8.1

    on May 27, 2025
22. kuny0707

    assigned

    halibobo1205

    on May 29, 2025
23. kuny0707

    added

    topic:consensus

    topic:DBDatabaseDatabase

    topic:deploymentconfiguration, startup commandconfiguration, startup command

    and removed

    v4.8.1

    on Jun 12, 2025
24. kuny0707

    added a parent issue on Jun 13, 2025

    • Tracking: prepare and manage release_v4.8.1 branch #6342
25. kuny0707

    moved this from In Progress to In Review in java-tronon Jun 30, 2025
26. halibobo1205

    closed this as completedon Jul 8, 2025
27. github-project-automation

    moved this from In Review to Done in java-tronon Jul 8, 2025
28. kuny0707

    removed a parent issue on Jul 8, 2025

    • Tracking: prepare and manage release_v4.8.1 branch #6342