Peter Rossbach wrote:
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.
Are you sure this is absolute necessity?
I agree something like that might be usable on a development server,
but on a production server? I'm not sure if your users will be happy
with loosing sessions in a middle of a transaction or order.
Again, disable works as expected. It will preserve exiting sessions
until session times out. When all existing sessions are gone, then you
can do with that node what ever you wish.
If you do not wish to wait, then simply disable and kill that instance.
The existing sessions will be failovered to another node with loosing
session data.
I see no reason whatsoever for introducing another 'immediate disable'
flag to the worker.
Regards,
Mladeb.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
