As part of the verification of the bundling of JMC with JDK 7u60 all the test suites for JMC 5.3.0 has been executed on JDK7u60, build 14. One unit test on JMC fails on JDK 7u60, and we think this may be an issue with the JDK rather than with JMC.

JMC displays some MBean attribute values which it reads over JMX from the JVM. Most of them are standard attribute values, but a few of them are synthetic. One such synthetic attribute value is java.lang.OperatingSystem#UsedPhysicalMemorySize. It's created by JMC by subtracting the value java.lang.OperatingSystem#FreePhysicalMemorySize from the value java.lang.OperatingSystem#TotalPhysicalMemorySize. The unit test that fails when running on JDK 7u60 verifies that this value is greater than 16 Mb (i.e. if the JVM reports that less than 16 Mb are in use, something is wrong and the test fails).

This does not fail on all platforms, however. We have seen on mostly on old platforms, most of which are not even supported by JDK 7u60. But there are some examples of failures also on supported platforms, such as Microsoft Windows 7 Professional, SP1, x86 (32-bit).

Unsupported platforms where we have also seen identical failures are:
Windows Server 2003,
Asianux Server 3 (Quartet)
SUSE Linux Enterprise Server 10 (i586) SP1

I've done one attempt to reproduce this manually, but without success.