[JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat (original) (raw)
Daniel Fuchs daniel.fuchs at oracle.com
Thu Jan 18 15:12:27 UTC 2018
- Previous message: RFR of 8194284: CheckRegisterInLog.java fails with java.lang.RuntimeException: CheckRegisterInLog got exception timeout 6480000ms out of range
- Next message: [JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: RFR of 8194284: CheckRegisterInLog.java fails with java.lang.RuntimeException: CheckRegisterInLog got exception timeout 6480000ms out of range
- Next message: [JDK 11] RFR: 8195096: Exception printed on console with custom LogManager on starting Apache Tomcat
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]