JDK-8031068 : java/util/logging/ParentLoggersTest.java: checkLoggers: getLoggerNames() returned unexpected loggers
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-12-27
  • Updated: 2021-03-10
  • Resolved: 2014-01-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 JDK 8 JDK 9
7u76Fixed 8u20Fixed 9 b02Fixed
Related Reports
Relates :  
JDK-8263382 - java/util/logging/ParentLoggersTest.java failed with "checkLoggers: getLoggerNames() returned unexpected loggers"
Relates :  
JDK-8029595 - Avoid cases of Logger being GC'ed in tests
Description
jdk8 b121
java/util/logging/ParentLoggersTest.java


# checkLoggers: getLoggerNames() returned unexpected loggers
# expected logger names (6):
 expNames[0] = 
 expNames[1] = global
 expNames[2] = myParentLogger
 expNames[3] = myParentLogger.myLogger
 expNames[4] = abc.xyz.foo
 expNames[5] = abc.xyz.foo.myBar.myLogger
# returned logger names (4):
  retNames[0] = global
  retNames[1] = abc.xyz.foo.myBar.myLogger
  retNames[2] = abc.xyz.foo
  retNames[3] = 
ParentLoggersTest: failed
Comments
This test creates two loggers without keeping any strong reference on them - thus allowing them to be arbitrarily gc'ed. See JDK-8029595. Holding a strong reference on these two loggers should solve the issue.
08-01-2014