Hello,<br><br>I agree with the fact that it could problematic to interrupt other web apps ...<br><br>But, how do you "redeploy" a web app ? With my own experience, I sometimes met some problems while upgrading a war or and unpacked web app while tomcat was running (incorrect class loaded, mix between old and new jars, new files unpacked but existing ones not being updated ...)<br>
<br>Cheers,<br>Benoit<br><br><div class="gmail_quote">2010/2/19 Marcus Better <span dir="ltr"><<a href="mailto:marcus@better.se">marcus@better.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 2010-02-19 09:37, Benoit GUERIN wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Please consider adding a trigger which can be used by web application packages to restart tomcat after they install or upgrade their files<br>
</blockquote>
<br>
Why is it not sufficient to redeploy the webapp that is being upgraded? Restarting the whole container may not be desirable, since it will interrupt other web apps.<br>
<br>
Cheers,<br><font color="#888888">
<br>
Marcus<br>
</font></blockquote></div><br>