Running the test,
sun/jvmstat/perfdata/PrologSanity/PrologSizeSanityCheck.java
on a solaris machine with lots of memory and cpus (and divided in to zones), this test reports sun.perfdata.used is too close to sun.perfdata.size causing the test to fail.

This test passes on "lesser" machines.

I do not know if the failure is related to running in a zone (fails both in GZ and one of the zones in the zonepool), or to the size of the machine (Oracle T2 256@3.6/512G Global Zone).

This link may be fleeting, but is to a typical jtr file:
http://java.se.oracle.com/mach5/view/9-dev-test/job/9-dev-tier2-solaris-sparc/99/artifact/JTwork/jdk_test/sun/jvmstat/perfdata/PrologSanity/PrologSizeSanityCheck.jtr/*view*/

Exception:

----------System.err:(13/1079)----------
java.lang.RuntimeException: jvmstat memory buffer usage approaching size: sun.perfdata.size=32768sun.perfdata.used=31768 : consider increasing PerfDataMemorySize
at PrologSizeSanityCheck.main(PrologSizeSanityCheck.java:72)
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:502)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92)
at java.lang.Thread.run(Thread.java:745)
 
jtr is attached.