JDK-8066122 : CollectionUsageThreshold.java times out when run with -XX:+ExplicitGCInvokesConcurrent
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P1
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-11-27
  • Updated: 2017-07-26
  • Resolved: 2015-01-15
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.
JDK 9
9 b47Fixed
Related Reports
Relates :  
JDK-7067973 - test/java/lang/management/MemoryMXBean/CollectionUsageThreshold.java hanging intermittently
Relates :  
JDK-8062450 - Timeout in LowMemoryTest.java
Relates :  
JDK-8064716 - TestHumongousShrinkHeap.java can not be run with -XX:+ExplicitGCInvokesConcurrent
Relates :  
JDK-8046351 - com/sun/management/GarbageCollectorMXBean/GarbageCollectionNotification[Content]Test.java should be quarantined
Relates :  
JDK-8029631 - CollectionUsageThreshold.java fails with -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent
Description
java/lang/management/MemoryMXBean/CollectionUsageThreshold.java times out once a week in the GC nightlies. It seems to be when run with -XX:+ExplicitGCInvokesConcurrent.
Comments
It can be done with ' @requires vm.opt.ExplicitGCInvokesConcurrent == "false" | vm.opt.ExplicitGCInvokesConcurrent == "null" ' jtreg tag expression.
02-12-2014
Failure reason was described in https://bugs.openjdk.java.net/browse/JDK-7067973 Suggested fix: remove VM option -XX:+ExplicitGCInvokesConcurren before test execution.
02-12-2014
Impact: High, nightly. Likelihood: Medium, when run with Explicit..., Workaround: High, unknown if using Explicit HMH --> P1
28-11-2014