Hi,
I have two webapps using Webwork, Maverick, Tomcat 4.1,
Hibernate, JSP views (but switching to freemarker soon).
These web applications have to be available 7 days a week,
24 hours a day but the problem is they need new features
almoust every day. But I am kind of tired of deploying new
Most servlet containers support hot-deployments. You should check out the
usergroups/ documentation of the servlet containers you are considering for
these features.
My experience with various servlet containers (like Resin, Jetty, Tomcat,
Websphere) is that it works allright if you play by the
Thank you all so far for these thoughs. Additional node
and load balancer would be good solution of course
and is definitely the right way to go.
The only problem is that there is not too much load
to balance :)
I now feel that our users can live with the fact that the
site is down for five
Operational issues are always highly specific to the environment you're running on,
unfortunately. There's always the old favorite Scheduled Downtime where you tell
people when the application will be offline for maintenance.
-Original Message-
From: Taavi Tiirik [mailto:[EMAIL
Taavi Tiirik wrote:
I have two webapps using Webwork, Maverick, Tomcat 4.1,
Hibernate, JSP views (but switching to freemarker soon).
These web applications have to be available 7 days a week,
24 hours a day but the problem is they need new features
almoust every day. But I am kind of tired of
Deploy in a clustered environment and bring down the cluster nodes one
at a time, upgrade that one, and bring it back online... You need a
server that can interact with your load balancer which sits in front
(either a hardware device or a plugin to a web server like Apache) so
that you can tell it
