Peter Rossbach ha scritto:
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... :-)
Yes, I didn't explained well... sorry :-)
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!
Mmmh, I think my context is reloadable, not sure... If it's not the only
way to update my jars is to restart Tomcat??
Bye,
Davide Romanini
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.9.2/55 - Release Date: 21/07/05
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
