I am trying to setup a cluster of two Tomcat 5.0.19 servers behind a
single instance of Apache.

We currently use the JK connector to connect Apache2 and a singel Tomcat
instance now, and would start to use it in load balancing mode with the
two Tomcat instances. We will need to start using JBoss Cache to keep
our Hibernate database caches synchronized.

My objectives would be:
 1) better through put (each Tomcat is on a separate machine)
 2) failover if one Tomcat goes down.
 3) the ability to do maintenance/fixes during the day without stopping
all activity.

My questions is about object #3. Currently if I deploy a fix (i.e. a new
webapp.war file), it restarts the context and my users get bumped off -
having to relogin, possibly loosing some work.

Ideally I was thinking that if a fix needs to be applied during the day
while users are using the system, I would:
1) Use the tomcat-deployer to "stop" one of the tomcat instances.
2) At this point all Tomcat traffic would be routed through the
remaining Tomcat server.
3) Use the tomcat-deployer to "deploy" and then "start" a fixed version
of the webapp.
   (Obviously the fixes are limite to logic changes, not database
changes).

Then I would repeat steps 1-3 for the second Tomcat instance.

Does it work this way? I've been reading the documentation and a couple
of articles and am not sure now.

I am also trying to understand the "deployer" element for the cluster.
This does not seem to be what I want as it will deploy the new war
locally and then immediately deploy it to the other members of the
cluster. BTW, the "deployer" element is not documented in my Tomcat
5.0.19 server.xml, but is in the later Tomcat 5.0.28. Does it work in
5.0.19. I can easily move to 5.0.28 in development, but our production
machines are only certified to run 5.0.19 (SuSE Linux Enterprise Server
9).

Thanks in advance for any advice/suggestions.

 - Richard


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to