autoDeploy underlying old failed versions

[Jeff Storey <st...@gmail.com>]

I have autoDeploy and undeployOldVersions enabled on my Tomcat server
and I am using parallel deployments. The issue I'm having is that old
versions that have errors in their startup are not removed. Let's say
I deploy the following apps:

myapp##001.war
myapp##002.war


If myapp#001.war failed during startup, and I deploy myapp##002,
requests are properly routed to the new version, by myapp#001 stays
around. When I then deploy myapp#003, myapp#002 is removed, but
myapp#001 is still left around.

Is there anything I can do to have deployments that failed still be removed?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: autoDeploy underlying old failed versions

[Mark Thomas <ma...@apache.org>]

On 13/01/2015 22:25, Jeff Storey wrote:
> I have autoDeploy and undeployOldVersions enabled on my Tomcat server
> and I am using parallel deployments. The issue I'm having is that old
> versions that have errors in their startup are not removed. Let's say
> I deploy the following apps:
> 
> myapp##001.war
> myapp##002.war
> 
> 
> If myapp#001.war failed during startup, and I deploy myapp##002,
> requests are properly routed to the new version, by myapp#001 stays
> around. When I then deploy myapp#003, myapp#002 is removed, but
> myapp#001 is still left around.
> 
> Is there anything I can do to have deployments that failed still be removed?

There is no option that will do this automatically.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org