-
Bug
-
Resolution: Fixed
-
P4
-
hs17
-
b01
-
x86
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2200247 | 7 | Tony Printezis | P4 | Closed | Fixed | b112 |
| JDK-2205844 | 6u25 | Tony Printezis | P4 | Closed | Fixed | b01 |
The tests
nsk/monitoring/MemoryPoolMBean/getCollectionUsageThreshold/getthreshold003
nsk/monitoring/MemoryPoolMBean/getUsageThreshold/getthreshold003
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold002
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold003
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold004
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold005
nsk/monitoring/MemoryPoolMBean/setUsageThreshold/setthreshold003
fail with message like "IllegalArgumentException was not thrown"
The MemoryBeans for G1 allow a usage of incorrect arguments.
See tests here:
http://vmsqe.russia.sun.com/execution/results/JDK6_UR/PROMOTION/VM//6u20/b01/G1GC/new_unknown_failures.html
http://vmsqe.russia.sun.com/execution/results/JDK6_UR/PROMOTION/VM//6u20/b01/G1GC/vm/solaris-i586/server/mixed/solaris-i586_server_mixed_nsk.monitoring.testlist/ResultDir/setthreshold002/setthreshold002.log
http://vmsqe.russia.sun.com/execution/results/JDK6_UR/PROMOTION/VM//6u20/b01/G1GC/vm/linux-amd64/server/comp/linux-amd64_server_comp_nsk.monitoring.testlist/ResultDir/setthreshold004/setthreshold004.log
The following tests failures in VM promotion testing (b99, G1) look similar to the failures above:
nsk/monitoring/MemoryPoolMBean/setUsageThreshold/setthreshold002
nsk/monitoring/MemoryPoolMBean/getUsageThreshold/getthreshold002
nsk/monitoring/MemoryPoolMBean/getCollectionUsageThreshold/getthreshold002
(http://vmsqe.russia.sun.com/execution/results/JDK7/PROMOTION/VM/b99/G1/vm/windows-i586/client/mixed/windows-i586_client_mixed_nsk.monitoring.testlist/analysis.html)
nsk/monitoring/MemoryPoolMBean/getCollectionUsageThreshold/getthreshold003
nsk/monitoring/MemoryPoolMBean/getUsageThreshold/getthreshold003
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold002
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold003
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold004
nsk/monitoring/MemoryPoolMBean/setCollectionUsageThreshold/setthreshold005
nsk/monitoring/MemoryPoolMBean/setUsageThreshold/setthreshold003
fail with message like "IllegalArgumentException was not thrown"
The MemoryBeans for G1 allow a usage of incorrect arguments.
See tests here:
http://vmsqe.russia.sun.com/execution/results/JDK6_UR/PROMOTION/VM//6u20/b01/G1GC/new_unknown_failures.html
http://vmsqe.russia.sun.com/execution/results/JDK6_UR/PROMOTION/VM//6u20/b01/G1GC/vm/solaris-i586/server/mixed/solaris-i586_server_mixed_nsk.monitoring.testlist/ResultDir/setthreshold002/setthreshold002.log
http://vmsqe.russia.sun.com/execution/results/JDK6_UR/PROMOTION/VM//6u20/b01/G1GC/vm/linux-amd64/server/comp/linux-amd64_server_comp_nsk.monitoring.testlist/ResultDir/setthreshold004/setthreshold004.log
The following tests failures in VM promotion testing (b99, G1) look similar to the failures above:
nsk/monitoring/MemoryPoolMBean/setUsageThreshold/setthreshold002
nsk/monitoring/MemoryPoolMBean/getUsageThreshold/getthreshold002
nsk/monitoring/MemoryPoolMBean/getCollectionUsageThreshold/getthreshold002
(http://vmsqe.russia.sun.com/execution/results/JDK7/PROMOTION/VM/b99/G1/vm/windows-i586/client/mixed/windows-i586_client_mixed_nsk.monitoring.testlist/analysis.html)
- backported by
-
JDK-2200247 G1: The MemoryPools are incorrectly supported for G1
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
JDK-6949298 The return type of MemoryPool::max_size() should be signed
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
(1 relates to)