Tomcat needs to be restarted 2 times when uploading new war file

When I put a new war file in the webapps directory and restart tomcat, my war file is exploded but the servlets are not available and their respective log files are not created in the logs directory. When I bounce tomcat again, then the servlets are available and the log files are created. I'm assuming I have setting(s) not correct within tomcat, but I'm not sure where to start.

Does anyone know the cause of my current situation? Or even what parameters to review?

New Additional/Comments: Our setup allows us to have our app 'myApp' be the default application that is seen at root of our URL. On the first starting of tomcat, I can get to myApp by going to /myApp/index.html - whereas on the second start of tomcat I can then just goto and myApp/index.html is dis开发者_如何学JAVAplayed.

My welcome file list is the 'myApp/index.html'

I had a similar problem with Tomcat 6.0.26. I worked around it by deleting the exploded webapps before copying the new war file to the webapps directory. Maybe a little kludgy, but it solved my problem.

http://tomcat.apache.org/tomcat-6.0-doc/config/context.html

antiJARLocking

If true, the Tomcat classloader will take extra measures to avoid JAR file locking when resources are accessed inside JARs through URLs. This will impact startup time of applications, but could prove to be useful on platforms or configurations where file locking can occur. If not specified, the default value is false.

have you set unpackWars and autoDeploy params to true in your server.xml file?

Try to do unpackwars=false and always make sure tomat is not running when you do deployment try to avoid hot deployment...