-
Enhancement
-
Resolution: Fixed
-
P4
-
20
-
b25
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8350957 | 17.0.16-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | master |
JDK-8351518 | 17.0.16 | Goetz Lindenmaier | P4 | Resolved | Fixed | master |
JDK-8350958 | 11.0.28-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | master |
JDK-8351141 | 8u461 | Ivan Bereziuk | P4 | Resolved | Fixed | master |
The usageTicks and totalTicks properties in the com.sun.management.internal.OperatingSystemImpl.ContainerCpuTicks class are not volatile, so different threads may not be able to get the latest cpu load when they get the cpu load.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Hard to reproduce, but usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks.
- backported by
-
JDK-8350957 usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks
-
- Resolved
-
-
JDK-8350958 usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks
-
- Resolved
-
-
JDK-8351141 usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks
-
- Resolved
-
-
JDK-8351518 usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks
-
- Resolved
-
- links to
-
Commit openjdk/jdk/dd18d76b
-
Commit(master) openjdk/jdk17u-dev/04a1b0d3
-
Review openjdk/jdk/11199
-
Review(master) openjdk/jdk17u-dev/3320