On 8/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi Hassan, > > I did exactly that way you described to me, > but the 2nd deployment still dosn't work properly.
You might want to create a very simple WAR file and see if it behaves the same way... > The only way that works (not always) is to delete the WAR file manually, > wait until the webapp is undeployed and then place the war file again. > INFO: Undeploying context [/xjosf] > com.magnasteyr.josf.InitLog4JPlugin ... try to clean up FileHandles for > context [XJOSF] > com.magnasteyr.josf.InitLog4JPlugin ... Clean up FileHandles finished for > context [XJOSF] Those two lines make me wonder -- since you're running Windows, you might look at antiJARLocking and antiResourceLocking here: <http://tomcat.apache.org/tomcat-6.0-doc/config/context.html> My feeling is that this is more likely app-related than config-related at this point; if you can create a WAR file reproducing the problem (without proprietary material/external dependencies) I'll be happy to try it. -- Hassan Schroeder ------------------------ [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]
