We have encountered issues with deploying unpacked war files on Windows
platforms: when redeploying webapps tomcat fails to clear out the unpacked
directory because windows locks some jar files. There is a
"antiResourceLocking" workaround but we decided to work with packed war
files in the end
--
> This problem is pretty common when restarting web applications. Libraries
> that use singletons etc. don't get reinitialized correctly when the web
> application is reloaded.
Blimey, that sounds like a serious flaw :S
Do you know why they don't get reinitialized properly? Could you give me
>> It looks like you have bad syntax in you log4j.properties file.
If that were the case, i would have expected it to fail the first time i
started the application?
to be clear, here are the steps to reproduce the error
[1] deploy an unpacked webapp "myapp" to $TOMCAT_HOME/webapps/myapp
[2] start
I am deploying an unpacked webapp directory to TOMCAT_HOME/webapps/myapp,
If i (stop and) start tomcat then my application runs fine and the logging
works fine. However if i stop the application (successfully, it seems) and
restart it using Tomcats manager app then I get the following error:
200
