Howdy,

>Wow, OK, thanks for the great insight. In other words, it's safe to
>assume to always restart Tomcat when deploying webapps. That, of
>course, is less than ideal. For testing, that just makes the
>development time longer (and more complicated, since now we have to
>remember to restart Tomcat every X deployment times). And for
>production, of course we don't want to take anything down.

In practice, it's also common to have one webapp per tomcat instance, so
that should anything go wrong (e.g. OutOfMemoryError, malicious code),
only one webapp is affected even if you have to restart the tomcat
server. So that above is not bad from that perspective.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)