[JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat

[Jason Mehrens]

Daniel,

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.

Jason
________________________________________
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
To: core-libs-dev
Subject: [JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat

Hi,

Please find below a proposed fix for:

8195096: Exception printed on console with custom LogManager on
          starting Apache Tomcat
https://bugs.openjdk.java.net/browse/JDK-8195096

webrev:
http://cr.openjdk.java.net/~dfuchs/webrev_8195096/webrev.00/

The issue appeared after the fix for
https://bugs.openjdk.java.net/browse/JDK-8191033
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"
property.

best regards,

-- daniel