File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Other Open Source Projects and the fly likes Log4j - configureAndWatch Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » Other Open Source Projects
Bookmark "Log4j - configureAndWatch" Watch "Log4j - configureAndWatch" New topic
Author

Log4j - configureAndWatch

Sylvia H Charbonneau
Ranch Hand

Joined: Jul 11, 2002
Posts: 37
Good Day All !!
Thanks for the replies with regards configuring Log4J. I've chosen to use a xml config file (after doing some experimenting with properties files). Hmm....I should probably add that to my last post.
I've encountered a new hiccup. My code uses the DOMConfigurator in the following fashion:
DOMConfigurator.configureAndWatch("log4j.xml");
Here's the hiccup, when I make changes to my file, they are not picked-up until I re-start Tomcat.
Any ideas ? I've done a little research, and haven't found anything related to bugs on this. Is there something I'm missing ?
S
Mert Nuhoglu
Greenhorn

Joined: Apr 22, 2004
Posts: 10
Hi, according to log4j faq, this method is unsafe in J2EE environment. There is a topic that explains how to resolve this problem by your own:

http://www.alegsa.com.ar/Visitas/index23/Alternative%20to%20change%20log4j%20logging%20level%20at%20runtime.php

Here is the quote from this topic:

In a J2EE application server, servlets may be unloaded at any time. You
know that before that happens, the destroy() method is called, so you can
clean up any background threads.

The Log4J thread that does that however, is not cleaned up. Or at least
there is no guarantee of that. Thus it is unsafe.

However, you can use the configuration methods of Log4J also to
REconfigure: start that background thread to signal changes in the logging
configuration yourself. You can then make sure that background thread is
stopped the the servlet initiating it is destroyed.


Best regards...

Mert
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Log4j - configureAndWatch