Scott M Stark wrote:
The AbstractWebDeployer/TomcatDeployer can inform tomcat that an
undeploy is begining. Are you looking for a distinction between an
unavailable app and one that is being redeployed?
Yes. I know that "there is no guarantee that the redeploy will succeed"
but in production that should not happend and even in this case the
customer probably prefer a 503 to a 404. (If the request cannot be
routed to another node).
I would think not as there is no guarantee that the redeploy will
succeed. I don't see that the MainDeployer needs to change, just the
The actual TomcatDeployer doesn't know that a redeploy is taking place
how could it inform Tomcat?
Jean-frederic Clere wrote:
> I am trying to find a way to improve the behaviour of mod_proxy httpd
> and JBossAS when an application is reployed.
> For the moment in MainDeployer.java we have something like:
> Due to this Tomcat doesn't know that the webapp is being redeployed and
> between the first undeploy() and end of deploy() is will return 404.
> It is possible to add a ContainerListener in Tomcat but the only things
> we get are removeChild and addChild events. It is possible to send a
> message to httpd to tell that the context of the webapp is not available
> in the node (to try to use another node of the cluster).
> I think that to make it clean we need to add a start_redeploy and
> end_redeploy event in Tomcat and modify MainDeployer and
> AbstractWebDeployer so that the redeploy event could reach the Tomcat
> jboss-development mailing list
jboss-development mailing list