: The point is I won't be able to start the server frequently to add new
: servlets, because our company needs the service 24/7.

Understood; please report your final solution, if possible.
Whenever an app steps out of the standard, there's an opportunity for
innovation. =)

One other idea: Tomcat clustering? e.g. reload Container1 while
Container2 continues to serve requests, then reload Container2 when
Container1 comes back up?

(Of course, this works only for changes to the servlet mappings; changes
to lower-level code libraries would require actual downtime.)

I had a similar setup w/ Weblogic a couple of years ago, also in a 24x7
shop. Being able to take down one member of the cluster in midday was
quite a treat.


-QM

--

software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


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