[JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat
jason_mehrens at hotmail.com
Thu Jan 18 21:19:37 UTC 2018
As long as the org.apache.juli.ClassLoaderLogManager overrides getProperty it shouldn't really matter what the value format is in the file as long as it is translated on return.
Is there a code path in j.u.l.LogManager that doesn't call getProperty? If so I would think that is the core issue.
From: core-libs-dev <core-libs-dev-bounces at openjdk.java.net> on behalf of Daniel Fuchs <daniel.fuchs at oracle.com>
Sent: Thursday, January 18, 2018 9:12 AM
Subject: [JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat
Please find below a proposed fix for:
8195096: Exception printed on console with custom LogManager on
starting Apache Tomcat
The issue appeared after the fix for
8191033: Regression in logging.properties: specifying .handlers=
for root logger (instead of handlers=) no longer works
Tomcat is apparently reusing the ".handlers" property, to specify
class names in a format that the LogManager cannot understand
(hence the exceptions logged on the console).
The proposed fix is to add a protected hook that subclass of
LogManager could extend to turn off parsing of the ".handler"
More information about the core-libs-dev