JDK-6830220 : Logging issues due to regression from bug fix 6797480.
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-04-14
  • Updated: 2014-03-17
  • Resolved: 2009-04-25
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.
Other JDK 6 JDK 7
5.0u65Fixed 6u75Fixed 7 b57Fixed
Related Reports
Relates :  
Description
Martin Buchholz <###@###.###> wrote:
 Our recent change
 changeset:   810:6eac3829cb41
 user:        martin
 date:        Tue Jan 27 15:04:30 2009 -0800
 summary:     6797480: Remove synchronization bottleneck in logger

 unfortunately introduced a serious bug.

 Logger.log should call Logger.getHandlers(), not Logger.handlers,
 because getHandlers may be overriden in a subclass.
 Notably, the root logger is such a subclass with a
 non-trivial getHandlers method.

 Here's the obvious fix, with a regression test that
 includes "penance" for our having broken j.u.l.
 by adding some much-needed  tests for never-before-exercised code.

 Please review and file a bug.

 PATCH is here:
 http://cr.openjdk.java.net/~martin/getHandlers

 Martin

Comments
EVALUATION See description.
21-04-2009

SUGGESTED FIX See Description.
14-04-2009