Davide Romanini schrieb:
Il giorno ven, 22/07/2005 alle 16.39 +0200, Peter Rossbach ha scritto:
Hey,
a) don't share things between cluster nodes!
You mean that Tomcat has problems using a shared filesystem???
No, tomcat has no problem with shared systems
b) before you change your lib at one node please shutdown the context
with manager app or ant tasks.
c) Release change at runtime with cluster is heavy and can not made
with the same nodes.
OK, when no class changed that used inside session replication, it
can be work!
d) Don't change all nodes at the same time.
Change one and
after restart context - see that all session comes in.
Then made change the others.
e) Build cluster domains and not running all nodes inside one cluster.
Tomcat cluster replicated all sessions between every node and
this is very memory intensive.
We are not using (for now) clustering features of Tomcat: we only have 6
instances of Tomcat running without knowing of the others, we have no
session replication.
OK, but the word "cluster" means to mean me that replication is
active... :-)
So the only solution to update my classes seems to be:
- unload the Axis context for each of the six machines
- update my jar file into WEB-INF/lib
- reload the Axis context for each of the six machines
Have you at the reloading="true" to your context.xml? At default tomcat
not look for class and jar updates!
Am I right?
I think no!
Bye,
Davide Romanini
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon: (49) 234 9413228
Mobil: (49) 175 1660884
E-Mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
