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 Summary: PropertyConfigurator.configureAndWatch thread not stopping Product: Log4j Version: 1.2 Platform: Other URL: http://marc.theaimsgroup.com/?t=104203519400006&r=1&w=2 OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Configurator AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have found the problem now: When using PropertyConfigurator.configureAndWatch(...), an instance of \ org.apache.log4j.helpers.FileWatchdog is instantiated and started in a separate \ thread. Redeployment of the application (meaning removal and deployment) does not \ remove this thread. So, after redeployment there are two such threads in the server's \ VM instance. The second one cannot access (and therefore not rename) the logfile, \ because it is locked by the remaining previous FileWatchDog-thread. Tricky and dangerous: I am constantly producing dead threads in the server's VM \ instance. Now, I have to find out how I can remove this thread at destroy time of my \ application ... If anybody knows how, please let me know. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
