-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b57
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8032033 | 6u75 | Dmeetry Degrave | P3 | Closed | Fixed | b05 |
JDK-8032034 | 5.0u65 | Dmeetry Degrave | P3 | Closed | Fixed | b04 |
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
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
- backported by
-
JDK-8032033 Logging issues due to regression from bug fix 6797480.
-
- Closed
-
-
JDK-8032034 Logging issues due to regression from bug fix 6797480.
-
- Closed
-
- relates to
-
JDK-6797480 Remove synchronization bottleneck in logger.
-
- Resolved
-