Glad you brought this back up P - was cursing this problem again yesterday. So if tomcat 6.0.29 is running and my foo webapp is deployed, if I dare copy in foo.war for auto re-deployment tomcat nukes my foo.xml context definition in conf/Catalina/HOST/ directory. Absolutely maddening. Is this expected behavior? It seems that you wouldn't want external configuration files removed on a redeployment. Of course I'm just testing out a new system and in production I'm not sure I'd be just copying in a new war file and calling that a redeployment... I'll change permissions on that file and see what happens. Thanks for your insights.
Jason On Wed, Sep 22, 2010 at 10:54 AM, Pid <p...@pidster.com> wrote: > On 10/09/2010 01:03, Jason Britton wrote: > > Could anyone give me an explanation what might cause my webapp's context > > configuration to be deleted out of the tomcat/conf/Catalina/[HOST]/ > > directory? I've got a foo.war file in the webapps directory, it gets > > exploded upon startup. It has its context definition residing in the file > > conf/Catalina/[HOST]/foo.xml. Every now and then foo.xml just gets up > and > > blown away from the tomcat/conf/Catalina/[HOST]/ directory, usually upon > a > > tomcat shutdown and startup. Any suggestions on what might be causing > this > > deletion and how to prevent it from occurring would be greatly > appreciated. > > Check the exact date of the file and system time. > > Make it readonly and look out for a stack trace. > > Seems like a weird issue for 6.0.29 - does it only occur during > shutdown, or startup as well (even weirder), any other time? > > > Running tomcat 6.0.29 on 64-bit RHEL 5.5. > > Much obliged. > > > p > >
