JDK-7075646 : G1: fix inconsistencies in the monitoring data
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs22
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-08-05
- Updated: 2013-10-04
- Resolved: 2012-01-23
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 | JDK 8 | Other |
|---|---|---|
7u2Fixed  |
8Fixed |
hs22Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
We're seeing some monitoring failures (mainly jstat-related) in the tmtools suite when running with G1. There are three separate reasons for the failures: 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.
Comments
|