Hey Mladen,
I used the tomcat at cluster mode, but your answer is a little bit to easy. Sticky session is the only way for the most applications to be consistens. Session replication is only a secondary feature when failure occured.
Why we can't add a flag that deactive a worker or change the semantic of disable?
Then all request goes to the other replication members in a cluster domain and restarting
is easy without risk and waiting time.
Peter
Mladen Turk schrieb:
Mladen Turk wrote:
Peter Rossbach wrote:
Hmm, that disabling feature not work at my configuration.
worker.node2.domain=A
You don't need a domain unless you have a session replication
Or you can just set jvmRoute="A" on each tomcat instance, make session replication, and then your config will work instantly when you disable one of the workers.
Regards, Mladen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
