This is related to Windows and your Context setup. For some reason Windows locks some jars (don't know why), so when you undeploy, the exploded war directory cannot be deleted.
Try setting up your context with the following settings. reloadable="true" antiResourceLocking="true" Let me know if this works. -----Original Message----- From: Tim Lucia [mailto:[EMAIL PROTECTED] Sent: Friday, June 09, 2006 6:44 AM To: 'Tomcat Users List' Subject: RE: Tomcat 5.5.17 - undeploy fails for app containing log4j.properties Do you have a LogFactory.release() in your ServletContextListener? i.e., mine says: public void contextDestroyed(ServletContextEvent sce) { logger.info("Application context destroyed."); LogFactory.release(Thread.currentThread().getContextClassLoader()); } Tim -----Original Message----- From: Hawkes, Rycharde (HP Labs) [mailto:[EMAIL PROTECTED] Sent: Friday, June 09, 2006 9:27 AM To: Tomcat Users List Subject: RE: Tomcat 5.5.17 - undeploy fails for app containing log4j.properties Windows XP SP2. The log4j.properties file is in a .jar file. All the other jar files are removed OK. They are all created in the same way during the build process so I don't think permissions are related to this. It seems that Tomcat's internal logging system is picking up the log4j.properties file in my jar file and not releasing it when I undeploy. Rych > -----Original Message----- > From: Marc Farrow [mailto:[EMAIL PROTECTED] > Sent: 09 June 2006 14:23 > To: Tomcat Users List > Subject: Re: Tomcat 5.5.17 - undeploy fails for app > containing log4j.properties > > What platform are you on? I do know that the manager app will say it > "undeployed" the application even if it does not have > permission to delete > all the files. Then when you try to deploy/undeploy again it > will fail. If > the log4j file is the only file not being deleted, then start with > permissions on this file. > > On 6/9/06, Hawkes, Rycharde (HP Labs) <[EMAIL PROTECTED]> wrote: > > > > I have a web-app that uses log4j-1.2.13. I specify my own > > log4j.properties file which is contained in a jar file in > WEB-INF/lib. > > > > Deployment is fine. When I try to undeploy everything > seems to work, > > and the manager confirms this, however one file remains - > the jar file > > containing the log4j.properties file! Any further attempts > to undeploy > > or deploy are unsuccessful and the server has to be stopped and the > > remaining file (and folder structure deleted). > > > > If I remove this file from the jar prior to the initial > deployment then > > undeploy works fine. > > > > Anyone else seen this/is this a known problem? > > > > Regards, > > > > Rych > > > > > > > > > -- > Marc Farrow > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:44897b5516561804284693! --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
