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 18:23 ------- The whole file watchdog mechanism used in v1.2.x is going to be replaced in v1.3 with new plugin functionality. A whole class of "watchdog" plugins will be implemented and available for use. They will be configurable via configuration files (at least xml configuration files) and much more control will be available to start/stop/restart them as needed. They will be shutdown as part of the repository shutdown process, etc. One of the reasons this is being done is because of this bug. Until then, I don't think there is an easy fix for this issue. I would suggest not using the configureAndWatch() mechanism, and instead include a servlet in your application that can be accessed via http requests to reload the log4j settings as needed. I would appreciate any feedback you might have on the new plugin architecture, and watchdogs in particular. There have been many discussion threads on the dev email list about the new watchdogs, though implementing them in the new plugin architecture still needs to be done. Soon. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
