Yes, that is the correct answer. As a matter of course you should never cause a file to be open for write from a) multiple web applications or b) multiple processes without using file locking. Note that RollingFileAppender clearly says it does not support file locking - there are just too many issues with it when trying to roll the files from multiple web apps or containers.
Ralph > On Mar 25, 2015, at 9:01 AM, Richard Kolb <rjdk...@gmail.com> wrote: > > Sorry, probably a silly question. > > The answer is drop log4j2 in the containers lib :) > > Regards, > Richard > On 25 Mar 2015 17:20, "Richard Kolb" <rjdk...@gmail.com> wrote: > >> Hi Remko, >> >> Just a quick question. >> I assume one global log4j2.xml in a container is a bad idea then. Assuming >> that the apps that log are in separate classloaders. >> >> Thanks. >> Richard. >> --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
