listeners will not be invoked on a state transfer, as it is not
considered an event.
when a new member joins the cluster, it requests a state transfer from
one of the other members.
Joseph Lam wrote:
I have it turned on already. But seems that after a node is killed and
then started up again,
I have it turned on already. But seems that after a node is killed and
then started up again, even though it can pick up the sessions from the
other nodes, my HttpSessionBindingListener and HttpSessionListener were
not called at all during the replication.
Joseph
On Fri, 25 Feb 2005, Filip
there is a flag you can set so that listeners don't get called, its optional
its called notifyListenersOnReplication, see server.xml for example,
default is true
Filip
Jesper Ekberg wrote:
Hello!
My first mail to this list. :)
I have read it for a long time tho.
We have a tried to cluster 3
there is a difference between a crashed tomcat and a shutdown tomcat.
Filip
Filip Hanik - Dev Lists wrote:
there is a flag you can set so that listeners don't get called, its
optional
its called notifyListenersOnReplication, see server.xml for example,
default is true
Filip
Jesper Ekberg
Hello!
My first mail to this list. :)
I have read it for a long time tho.
We have a tried to cluster 3 Tomcat 5.5.7 machines and I found that
HttpSessionBindingListener will be notified when the session is replicated and
the machine crashes.
I think this must be a bug??
The scenario:
3 Tomcat
