Re: loggerContext for container shared lib

Thanks for looking into this! I do have a log4j2.xml in tomcat/lib, was thinking that would be used by the common classloader for the commomLib log... I guess the problem is that the commonLib classes were only referenced by the webapp code, thus the loggerContext for the commonLib was created

Re: loggerContext for container shared lib

; > On Oct 5, 2017, at 1:31 AM, "billok...@gmail.com"<billok...@gmail.com> > > wrote: > > > > Thanks for looking into this! > > > > I do have a log4j2.xml in tomcat/lib, was thinking that would be used by > > the common classloader for the c

ConfigLocationUri jndi vs file

Hi, Using log4j2 v2.3 (and also tested with v2.9.1), when deploying a war with the following config in servlet 3.0 web.xml file: log4j2 configuration file log4jConfiguration WEB-INF/classes/log4j2.xml when tried to monitor the logger via JMX, noticed that the

Re: ConfigLocationUri jndi vs file

I think I figured out the issue, seems related to the log4jConfiguration setting... (sorry messed up the reply last time) - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail:

Re: ConfigLocationUri jndi vs file

On 2017-09-26 12:11, "billok...@gmail.com"<billok...@gmail.com> wrote: > Hi, > > Using log4j2 v2.3 (and also tested with v2.9.1), when deploying a war with > the following config in servlet 3.0 web.xml file: > > > log4j2 configuration file &

Issue with log4jConfiguration setting

Hi, With log4j2 v 2.9.1 (same issue in previous version 2.6), by putting the log4j2.xml file in WEB-INF/classes, log4j will eventually locate that config file as 'file:/' ConfigLocationUri: file:/opt/tomcat/webapps/log4jTest/WEB-INF/classes/log4j2.xml and the config file monitoring

issues with log4j-web.jar deployed location

Hi, should log4j-web.jar be packaged in individual web app WEB-INF/lib or can it be deployed in tomcat/lib (to be shared by several web apps)? Tested with log4j2 v2.6 and latest v2.9.1, and noticed that it seems to work either way when a webapp is first deployed. BUT if having a log4j2.xml

Re: issues with log4j-web.jar deployed location

thanks a lot for the prompt reply and explanation! the reason for using the log4j-web is to have each webapp logs to it's own log file, thus the ${web:contextPath}.log. But packaging the log4j-web in the webapp/lib would make sense. -Bill

loggerContext for container shared lib

Hi, we have multiple webapps, say, webapp1 and webapp2, that use a shared apache lib (say commonLib, which also uses log4j logging) that deployed as jndi resource in tomcat (thus was put in tomcat/lib), and followings are our log4j jars deploy location: tomcat/lib: - log4j-core.jar,

Re: loggerContext for container shared lib

Note: in the above example, 3 loggerContext will be created, as: - webapp1 - webapp2 - 6dde5c8d (for the commonLib that uses webapp1 log4j2.xml) - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional