Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2216140 | 8 | Tony Printezis | P3 | Resolved | Fixed | b10 |
JDK-2219684 | 7u4 | Tony Printezis | P3 | Closed | Fixed | b01 |
JDK-2216343 | 7u2 | Tony Printezis | P3 | Closed | Fixed | b11 |
JDK-2214542 | hs22 | Tony Printezis | P3 | Closed | Fixed | b08 |
a) the G1 monitoring data is wrong
b) the G1 monitoring data is correct but different/inconsistent compared to what the other GCs do
c) the tests do not know how to handle G1 when needing to get GC-specific data
This CR will try to fix the failures that fall into the a) category and as many failures that fall into the b) category as it's practical to do from within G1 (for the latter we'll have to "massage" the way G1 generates data to look more consistent with what the other GCs do). The rest will be covered by separate CRs.
The Comments section has more detailed information on specific test failures.
- backported by
-
JDK-2216140 G1: fix inconsistencies in the monitoring data
- Resolved
-
JDK-2214542 G1: fix inconsistencies in the monitoring data
- Closed
-
JDK-2216343 G1: fix inconsistencies in the monitoring data
- Closed
-
JDK-2219684 G1: fix inconsistencies in the monitoring data
- Closed
- relates to
-
JDK-6946417 G1: Java VisualVM does not support G1 properly.
- Closed
-
JDK-6946385 G1: jstat does not support G1 GC
- Closed
-
JDK-6966967 G1: SA: jmap and jstack do not work
- Closed
-
JDK-7097048 G1: extend the G1 SA changes to print per-heap space information
- Closed
-
JDK-7092309 G1: introduce old region set
- Closed