JDK-7196801 : NPG: Fix java/lang/management/MemoryMXBean/LowMemoryTest2
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 8
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-09-07
  • Updated: 2014-04-07
  • Resolved: 2013-10-14
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.
8 b113Fixed
Related Reports
Blocks :  
Blocks :  
Blocks :  
Blocks :  
Duplicate :  
Duplicate :  
Relates :  
The java/lang/management/MemoryMXBean/LowMemoryTest2 is timing out.  It is
spending lots of time in GC but it is making progress.  Needs investigation.

I plan to push this the next week.

Stefan - do you plan to push this for 8 or should we file for deferral?

Embedded: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=290074.JAVASE_EMBEDDED_PROMOTION_TESTCYCLE_8_ALL-4248 java/lang/management/MemoryMXBean/LowMemoryTest2.sh

Suggested fix, after JDK-8024547 has been fixed.

Coleen provided a patch, that I've slightly altered, to fix the test. However, the test will fail until JDK-8024547 has been resolved.

After the Metaspace memory pools are in we can see if it's possible to make this test run properly

EVALUATION It appears that the test is trying to load classes in order to get a MXBean memory usage theshold notification for non-heap memory. Since the removal of the perm gen MXBean the code cache is the only non-heap MXBean with usage threshold capabilities. Thus the test loads classes until it times out or until the counter for the class names wraps around. I'd say that there's no good way to fix this test other than removing it. Trying to fill up the code cache in order to get a notification seems to be very fragile, with the test being run both with and without -Xcomp etc.