Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8253134

JMM_VERSION should remain at 0x20020000 (JDK 10) in JDK 11

    XMLWordPrintable

Details

    Backports

      Description

        JDK-8231209, which was originally pushed to JDK 14, has been backported to 11.0.9 and 11,0.10-oracle. Those backports changed JMM_VERSION from 0x20020000 (JDK 10) to 0x20030000 (JDK 14), which introduced an incompatibility that was overlooked in the backport CSRs JDK-8247807 (11.0.9) and JDK-8248871 (11.0.10-oracle). JDK 11 users checking for JMM_VERSION == 0x20020000 will find 0x2003000 instead and possibly abort. The issue was first noticed as part of reviewing a backport of JDK-8185003 to JDK 8: see the Description in the corresponding CSR JDK-8251498.

        For the reasons detailed there, JMM_VERSION in JDK 11 should be reverted to 0x20020000 (JDK 10), and the @since javadoc tag for com.sun.management.ThreadMXBean.getCurrentThreadAllocatedBytes should be changed from 14 to 11.0.9.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8253574 JMM_VERSION should remain at 0x20020000 (JDK 10) in JDK 11

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8270370 JMM_VERSION should remain at 0x20020000 (JDK 10) in JDK 11

            • P3 - Major loss of function.
            • Resolved
            csr for

            CSR - null JDK-8253136 JMM_VERSION should remain at 0x20020000 (JDK 10) in JDK 11

            • P3 - Major loss of function.
            • Closed
            relates to

            Enhancement - null JDK-8231209 [REDO] JDK-8207266 ThreadMXBean::getThreadAllocatedBytes() can be quicker for self thread

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            CSR - null JDK-8251498 JMX: Add a version of ThreadMXBean.dumpAllThreads with a maxDepth argument

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

            Activity

              People

                phh Paul Hohensee
                phh Paul Hohensee
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: