removed the log4j2.component.properties files and added following to
$CATALINA_HOME/bin/setenv.sh (works):export CATALINA_OPTS="$CATALINA_OPTS
-Dlog4j2.enableJndiContextSelector=true"
export CATALINA_OPTS="$CATALINA_OPTS
-DLog4jContextSelector=org.apache.logging.log4j.core.selector.JndiContextSe
Strike my previous comment regarding testing1 (it's not configured for separate
logging and is likely logging to catalina.out).Any possible reasons why
potentially log4j2.component.properties is not being scanned or fail to read
key/value pairs in WEB-INF/classes dir? Does it depend on the depl
There seems to be an issue with reading from the
WEB-INF/classes/log4j2.component.properties file (root cause unknown
currently).If I add the following to $CATALINA_HOME/bin/setenv.sh file:export
CATALINA_OPTS="$CATALINA_OPTS
-DLog4jContextSelector=org.apache.logging.log4j.core.selector.JndiCon
Sorry, just realized a possibly important detail. In dev envmt, I am using
slf4j-api-2.0.6.jar, in QA we are using slf4j-api-1.7.25.jar.When log4j2.debug
was enabled in previous testing, I see the following logging/notes:DEBUG
StatusLogger Building Plugin[name=logger,
class=org.apache.logging.
Hi,I have been able to successfully configure and log separately for multiple
web apps deployed to same Tomcat 7.0.84 container in dev environment (Windows
11 w/ cygwin). Now trying to do the same testing in QA environment with Tomcat
7.0.82 (Linux) and having issue below at startup. I doubt i
