Hi,
>
>Log4jInit
>Log4jInit
>
>log4j-init-file
>WEB-INF/log4j.config
>
>1
>
Just keep in mind that the server is not required to keep
load-on-startup servlets in memory.
Have you tried using PropertyConfigurator.configureAndWatch(String
configFilename, long delay) instead of configure(String filename)?
On Wed, 2002-10-23 at 18:00, Carson, Chuck wrote:
>
> I am using a servlet to intialize log4j as so:
>
> public class Log4jInit extends HttpServlet
> {
> publ
My current solution is to deploy the Log4j config file separately from the WAR
file and use configureAndWatch. The idea is that the config file gets deployed
to a directory that's included on the app server's classpath. The app can then
locate the file through ClassLoader.getResource and URL.get
