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??? > 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. 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 Am I right? Bye, Davide Romanini --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
