Re: System.gc() causes for jcl (BufferPoolMXBean)

2015-06-18 Thread Bernd Eckenfels
Hello, Am Sat, 6 Jun 2015 19:07:07 +0200 schrieb Bernd Eckenfels : > - why is BufferPoolMXBean not tracking allocation failures, allocation > count, alignment flag and maximum size (maybe even modifyable). > Would it be worth to contribute something in this area or is that > supposed to be cove

Re: RFR 8129215: com.sun.jmx.mbeanserver.Introspector may provide results inconsistent with the JavaBeans Introspector

2015-06-18 Thread Daniel Fuchs
On 6/18/15 7:16 PM, Jaroslav Bachorik wrote: On 18.6.2015 18:47, Daniel Fuchs wrote: Hi Jaroslav, I haven't looked at the code, but if I understand well, that would be a spec change. Attribute names are case sensitive in JMX. getFoo() => attribute named "Foo" getfoo() => attribute named "fo

Re: RFR 8129215: com.sun.jmx.mbeanserver.Introspector may provide results inconsistent with the JavaBeans Introspector

2015-06-18 Thread Jaroslav Bachorik
On 18.6.2015 18:47, Daniel Fuchs wrote: Hi Jaroslav, I haven't looked at the code, but if I understand well, that would be a spec change. Attribute names are case sensitive in JMX. getFoo() => attribute named "Foo" getfoo() => attribute named "foo" Are you proposing to change that? In thi

Re: RFR 8129215: com.sun.jmx.mbeanserver.Introspector may provide results inconsistent with the JavaBeans Introspector

2015-06-18 Thread Daniel Fuchs
Hi Jaroslav, I haven't looked at the code, but if I understand well, that would be a spec change. Attribute names are case sensitive in JMX. getFoo() => attribute named "Foo" getfoo() => attribute named "foo" Are you proposing to change that? best regards, -- daniel On 18/06/15 18:39, Jar

RFR 8129215: com.sun.jmx.mbeanserver.Introspector may provide results inconsistent with the JavaBeans Introspector

2015-06-18 Thread Jaroslav Bachorik
Please, review the following change Issue : https://bugs.openjdk.java.net/browse/JDK-8129215 Webrev: http://cr.openjdk.java.net/~jbachorik/8129215/webrev.00 The JMX Introspector will try to use the JavaBeans introspector whenever possible, delegating the requests for the property getter/setter

Re: RFR 8080138: sun/management/jmxremote/startstop/JMXStartStopTest.java failed with java.lang.Error intermittently

2015-06-18 Thread Staffan Larsen
Looks good! Thanks, /Staffan > On 18 jun 2015, at 13:01, Jaroslav Bachorik > wrote: > > Please, review the following test change > > Issue : https://bugs.openjdk.java.net/browse/JDK-8080138 > Webrev: http://cr.openjdk.java.net/~jbachorik/8080138/webrev.00 > > The test is using DCMD to turn

Re: RFR 8081634: Concurrent usage of a StringBuilder causes test intermittent failures

2015-06-18 Thread serguei.spit...@oracle.com
Looks good. Thanks, Serguei On 6/17/15 11:54 AM, Jaroslav Bachorik wrote: Please, review the following test change Issue : https://bugs.openjdk.java.net/browse/JDK-8081634 Webrev: http://cr.openjdk.java.net/~jbachorik/8081634/webrev.00 This is an issue in the utility class providing the func

RFR 8080138: sun/management/jmxremote/startstop/JMXStartStopTest.java failed with java.lang.Error intermittently

2015-06-18 Thread Jaroslav Bachorik
Please, review the following test change Issue : https://bugs.openjdk.java.net/browse/JDK-8080138 Webrev: http://cr.openjdk.java.net/~jbachorik/8080138/webrev.00 The test is using DCMD to turn on the management agent. It seems that under certain conditions the time needed to actually startup th

Re: RFR: JDK-8122944 perfdata used is seen as too high on sparc zone with jdk1.9 and causes a test failure

2015-06-18 Thread serguei.spit...@oracle.com
It looks good to me. Thanks, Serguei On 6/18/15 1:56 AM, Staffan Larsen wrote: This test is failing on machines with lots of CPUs since we create lots of compiler threads and there are 4 perf counters for each compiler thread. This eats memory. A simple solution is to just bump the default

RFR: JDK-8122944 perfdata used is seen as too high on sparc zone with jdk1.9 and causes a test failure

2015-06-18 Thread Staffan Larsen
This test is failing on machines with lots of CPUs since we create lots of compiler threads and there are 4 perf counters for each compiler thread. This eats memory. A simple solution is to just bump the default for PerfDataMemorySize from 32K to 64K - "that should be enough for everyone.” Tha

Re: RFR 8081634: Concurrent usage of a StringBuilder causes test intermittent failures

2015-06-18 Thread Staffan Larsen
Looks good! Thanks, /Staffan > On 17 jun 2015, at 20:54, Jaroslav Bachorik > wrote: > > Please, review the following test change > > Issue : https://bugs.openjdk.java.net/browse/JDK-8081634 > Webrev: http://cr.openjdk.java.net/~jbachorik/8081634/webrev.00 > > This is an issue in the utility