Added PlatformLoggingMXBeanTest to the 7067691 bug fix,
e.g. instance variables for Logger variables to prevent premature
weak reference collection.
http://cr.openjdk.java.net/~gadams/7067691/
Fresh webrevs for the other work in progress bug fixes.
http://cr.openjdk.java.net/~gadams/6731620/
http://cr.openjdk.java.net/~gadams/6818464/
http://cr.openjdk.java.net/~gadams/6860309/
http://cr.openjdk.java.net/~gadams/7084033/
On 11/10/11 09:41 AM, Gary Adams wrote:
On 11/ 8/11 11:13 PM, Mandy Chung wrote:
Thanks for picking up this bug and fixing this intermittent issue.
PlatformLoggingMXBeanTest.java in the same directory has the same issue.
It'd be good to fix that with the same CR. These tests were copied from
test/java/util/logging/LoggingMXBeanTest.java. I haven't looked in details
but I wonder why the test/java/util/logging tests don't have this
intermittent issue and I suspect it holds a strong reference.
I attempted to break PlatformLoggingMXBeanTest.java with a generous
application of
GC calls, but I could not get it to fail in the same manner as the other test.
It may be
failing due to a different condition.
