Filip,
I've got a basic implementation of this. Since I didn't want to change
Tomcat code, this is not the most elegant design.
Here's what I've done:
I created a ManualFailoverManager class, which extends StandardManager. This
is a copy of the BackupManager, with these changes:
1) In the req
Ok, the backup manager which does two things
1. [every request] it selects a backup node and each time the session
changes it publishes the delta to the back up node
2. [one time] upon session creation it also notifies the other nodes
with the location of the backup node for session X
should
Filip,
Thanks. If you could elaborate some more, then maybe I can go ahead and
implement this, and I'd be happy to send you the result, so you can use it
and save yourself some of the work.
Naaman
Filip Hanik - Dev Lists wrote:
>
> nlif wrote:
>> Hi all,
>>
>> We intend to run in a cluster,
Thanks, Chris,
Yes, this is an option, but we prefer being able to offload session at will.
However, if that proves to be too difficult to do, we may settle for the
behavior you describe.
Naaman
Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nilf,
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nilf,
nlif wrote:
> We intend to run in a cluster, with stickiness enabled, and without
> replication. This of course does not give us failover capabilities, in case
> of a server crash, but it is sufficient for our needs.
>
> However, we would like
nlif wrote:
Hi all,
We intend to run in a cluster, with stickiness enabled, and without
replication. This of course does not give us failover capabilities, in case
of a server crash, but it is sufficient for our needs.
However, we would like to be able to transfer all sessions currently on on
