JDK-8031036 : Used for the fix push for JDK-8038322: CounterMonitorDeadlockTest.java fails intermittently, presumed deadlock
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-12-25
  • Updated: 2015-09-29
  • Resolved: 2014-05-02
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 8 JDK 9
8u60Fixed 9 b13Fixed
Related Reports
Duplicate :  
JDK-8038322 - CounterMonitorDeadlockTest.java fails intermittently, presumed deadlock
Relates :  
JDK-8047295 - com/sun/management/OperatingSystemMXBean/GetCommittedVirtualMemorySize.java failed on jdk9 nightly testing
Description
This bug was wrongly used for the fix push for JDK-8038322, JDK-8047295 was created with same issue .

Here is the original description:
com/sun/management/OperatingSystemMXBean/GetCommittedVirtualMemorySize.java failed on 8b121

java.lang.RuntimeException: Committed virtual memory size illegal value: 2334003200 bytes (MIN = 1; MAX = 2116968448)
	at GetCommittedVirtualMemorySize.main(GetCommittedVirtualMemorySize.java:91)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:744)
Comments
This bugid was originally used to track the problem described in JDK-8047295, but was then mistakenly used in the commit comment for the changeset that fixed JDK-8038322. The problem originally reported in this bug (JDK-8031036) is therefore now tracked by JDK-8047295.
19-09-2014
From failure on 13June2014 gc-baseline nightly testing java.lang.RuntimeException: Committed virtual memory size illegal value: 2595737600 bytes (MIN = 1; MAX = 2116968448) at GetCommittedVirtualMemorySize.main(GetCommittedVirtualMemorySize.java:91) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)java.lang.RuntimeException: Committed virtual memory size illegal value: 2595737600 bytes (MIN = 1; MAX = 2116968448) at GetCommittedVirtualMemorySize.main(GetCommittedVirtualMemorySize.java:91) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:484) at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94) at java.lang.Thread.run(Thread.java:745) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:484) at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94) at java.lang.Thread.run(Thread.java:745)
16-06-2014
The test failed on: if (size < MIN_SIZE_FOR_PASS || size > max_size_for_pass) the test got at first "max_size_for_pass", then got "size" by calling: long size = mbean.getCommittedVirtualMemorySize(); the problem might be that the operation getCommittedVirtualMemorySize() made the VM allocate more memory. A possible solution is to get "size" before max_size_for_pass, or ask the test to warm up at first by repeating several time getting operations before real testing.
26-12-2013