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 ------- Additional Comments From [EMAIL PROTECTED] 2003-01-09 11:37 ------- For current productive installations, one cannot rely on having a servlet-2.3- compliant environment. One can generally only rely on the availability of the destroy-method per servlet instance. Therefore some sort of registration procedure is needed. Each object (it does not need to be a request thread handled by a servlet), that requires a properly initialized log4j-environment and cannot rely on others to do so, registers with the watchdog thread (if not present, it is created). In its finalize()-method (or similar end-of-lifecycle method), it unregisters. If no more registered objects are present, the FileWatchdog-thread terminates. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
