On Tue, 2011-08-23 at 10:11 +0100, Alan Bateman wrote:
> Mandy Chung wrote:
> > Steve,
> >
> > I have prepared a patch from your contribution [1] to fix:
> >7068328: BufferPoolMXBean and PlatformLoggingMXBean getObjectName
> > may return null
> >
> > Webrev at:
> >http://cr.openjdk.java.ne
Mandy Chung wrote:
Steve,
I have prepared a patch from your contribution [1] to fix:
7068328: BufferPoolMXBean and PlatformLoggingMXBean getObjectName
may return null
Webrev at:
http://cr.openjdk.java.net/~mchung/7068328/webrev.00/
I have modified the fix to move the "result = objname"
Steve,
I have prepared a patch from your contribution [1] to fix:
7068328: BufferPoolMXBean and PlatformLoggingMXBean getObjectName
may return null
Webrev at:
http://cr.openjdk.java.net/~mchung/7068328/webrev.00/
I have modified the fix to move the "result = objname" assignment before
On 19/07/11 14:30, Alan Bateman wrote:
Steve Poole wrote:
On 19/07/11 05:09, Alan Bateman wrote:
(cc'ing serviceability-dev)
Thanks Steve, looks like this crept as part of some refactoring work
[1]. Looks like PlatformLoggingMXBean has the same issue. I've
created the following bug to track
Steve Poole wrote:
On 19/07/11 05:09, Alan Bateman wrote:
(cc'ing serviceability-dev)
Thanks Steve, looks like this crept as part of some refactoring work
[1]. Looks like PlatformLoggingMXBean has the same issue. I've
created the following bug to track it:
7068328: BufferPoolMXBean and Plat
I wasn't sure of the testcase form to use for a
multithreaded problem - I will be curious to see how it ends up.
-Alan
[1] http://hg.openjdk.java.net/jdk7/jdk7/jdk/rev/77dd50ba670b
Original Message
Subject: java.nio.BufferPoolMXBean getObjectName() occasionally
ret
k7/jdk/rev/77dd50ba670b
Original Message
Subject: java.nio.BufferPoolMXBean getObjectName() occasionally returns
null
Date: Mon, 18 Jul 2011 22:54:35 +0100
From: Steve Poole
To: [email protected]
Hi all, a small fix to a race condition that occurs under extreme and
