initialize Log4j using the Log4jConfigurator class,
* this will be done for you. The servletContext property is static;
* because each webapp gets its own classloader there is a one-to-one
* mapping between servlet contexts and instances of
* ServletLogAppender.class.
*
* @author Bill Schneider
To get around the problems I was having with log4j in a clustered
environment (multiple processes on one filesystem), I wrote a new appender
that writes to the servlet log as if you called servletContext.log(...).
Has anyone thought of doing this before? Hadn't seen much on the lists
about it. I
Hey,
I'm using log4j in a clustered J2EE webapp environment, where there are 4
concurrent JVM processes running the same webapp and using the same log4j
configuration, appending to the same log file. We're using a
DailyRollingFileAppender, so the file should be rolled at midnight every
night.
