The difference is:
with another .war file than ROOT.war it is calling /list twice, then first undeploys the deployed webapp, and then deploys it.
With ROOT.war it only calls /list once and immediatly tries to deploy.
I guess, it cannot find the deployed ROOT in the list (does it look for the "/" path?) and therefore thinks, that the webapp currently is not deployed and therefore immediatly tries to deploy ?
Hi,
we have problems re-deploying ROOT.war on tomcat8. I don't know, if it is working on other tomcats.
If I look into the access.log I notice the following: upon a working deployment:
but for ROOT.war
The difference is: with another .war file than ROOT.war it is calling /list twice, then first undeploys the deployed webapp, and then deploys it.
With ROOT.war it only calls /list once and immediatly tries to deploy. I guess, it cannot find the deployed ROOT in the list (does it look for the "/" path?) and therefore thinks, that the webapp currently is not deployed and therefore immediatly tries to deploy ?
Doesn't anybody else have this problem?
Thanks! Martin