You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/01/08 20:46:40 UTC

DO NOT REPLY [Bug 15896] - PropertyConfigurator.configureAndWatch thread not stopping

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15896>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15896

PropertyConfigurator.configureAndWatch thread not stopping

hoju@visi.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hoju@visi.com
            Summary|PropertyConfigurator.configu|PropertyConfigurator.configu
                   |reAndWatch thread not       |reAndWatch thread not
                   |stopping                    |stopping



------- Additional Comments From hoju@visi.com  2003-01-08 19:46 -------
Well, if you are talking about a servlet application, you should be able to 
call LogManager.shutdown() in the contextDestroyed() method of a servlet 
context listener (beginning with servlet-2.3).  That is what I do.  Any reload 
or removal of the application without shutting down the server should then 
clean up log4j so it will be ready for the next load.

Does that solve the issue for you?

Jake

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>