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:
This bug is linked to fixes in https://ops4j1.jira.com/browse/PAXLOGGING-238
, pax-logging doesn't read JUL properties configuration... What's your setup and where do you want to configure JUL for pax-logging?
I used this function when doing changes related to PAXLOGGING-252. It should help: