Mikolaj Rydzewski wrote:
I have added following attribues to |META-INF/context.xml and it helped:
||unpackWAR=false ||antiJARLocking=true ||antiResourceLocking=true
|
Sorry for some strange characters, correct line is:
unpackWAR=false antiJARLocking=true antiResourceLocking=true
Please
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
Dear list,
I have an application (ApplicationA) running on Tomcat 6.0.16. Occasionally,
when Tomcat is restarted, the contents of the folder where the exploded war
resides becomes corrupt. I.e. jars that can be found underneath
tomcat/webapps/ProjectA/WEB-INF/lib are removed, resulting in
