Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8351143 | 24.0.2 | Ramkumar Sunderbabu | P2 | Resolved | Fixed | b01 |
JDK-8351245 | 24.0.1 | Nibedita Jena | P2 | Closed | Fixed | b09 |
We are facing an issue with MBean where ProcessCPULoad and CpuLoad values are displayed as -1 which is default value and even after refreshing the values are not getting updated.
We are using these MBean attributes to display CPU Usage in our application Java Mission Control (JMC). Since the values are always -1 , we are getting a blank dial on our application which is a major issue from JMC perspective.
We have tried to analyze the issue as per our best understanding. We have identified the attributes were loaded properly till JDK 24 b12 and there is some issue from JDK 24 b13 build onwards.
We are looking for some help in understanding and fixing the issue.
- backported by
-
JDK-8351143 OperatingSystemMXBean CpuLoad() methods return -1.0 on Windows
-
- Resolved
-
-
JDK-8351245 OperatingSystemMXBean CpuLoad() methods return -1.0 on Windows
-
- Closed
-
- caused by
-
JDK-8336289 Obliterate most references to _snprintf in the Windows JDK
-
- Resolved
-
- relates to
-
JDK-8350818 Improve OperatingSystemMXBean cpu load tests to not accept -1.0 by default
-
- Resolved
-
-
JDK-8350939 Revisit Windows PDH buffer size calculation for OperatingSystemMXBean
-
- Resolved
-
-
JDK-8351002 com/sun/management/OperatingSystemMXBean cpuLoad tests fail intermittently
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk24u/d8d055ed
-
Commit(master) openjdk/jdk/197004f4
-
Review(master) openjdk/jdk24u/103
-
Review(master) openjdk/jdk/23832