Log level values are not case insensitive for JUL

Description

Log4J treats the log level values as case insensitive. So it is possible to give it a value 'ERROR' as well as 'error'.

Pax Logging behaves in the same way when the underlying logger is Log4J, but not when the underlying logger is the Java Util Logging. This means that when such a log level is defined as 'error', it will fall back to INFO instead, which is very strange behavior.

See here that Log4J is case insensitive:
https://github.com/apache/logging-log4j2/blob/log4j-2.9.0/log4j-api/src/main/java/org/apache/logging/log4j/Level.java#L287

This bug is linked to fixes in https://ops4j1.jira.com/browse/PAXLOGGING-238

Environment

None

Activity

Show:
Grzegorz Grzybek
April 19, 2019, 12:13 PM

, pax-logging doesn't read JUL properties configuration... What's your setup and where do you want to configure JUL for pax-logging?

Grzegorz Grzybek
June 3, 2019, 3:08 PM

I used this function when doing changes related to PAXLOGGING-252. It should help:

Assignee

Grzegorz Grzybek

Reporter

Niels Berghen

Fix versions

Labels

None

Priority

Major
Configure