Kenneth Westelinck wrote:
Deleting the exploded war folder and restarting Tomcat resolves this issue
... but this is not an ideal situation of course. This error ocurs on my
client's machine. I was not able to reproduce this on our local development
machine. The client's machine is running Windows XP, SP3, no virusscanner.
Is there anyone else on the list that has seen this behaviour?
Windows OS uses different file locking (it applies to jar files)
mechanism that e.g. Linux. Sometimes it makes problems with
undeploying/removing application.
I had once similiar case. Struts/hibernate application, there're many
notes, that due to some reasons Tomcat is unable to completely undeploy
such application. Result is that it's impossible to completely remove
application's folder. I have added following attribues to
|META-INF/context.xml and it helped:
||unpackWAR="false" ||antiJARLocking="true" ||antiResourceLocking="true"
|
--
Mikolaj Rydzewski <[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]
