Andrew Hole wrote:
I have both tomcat instances on the same machine, and tcpListenPort are
different on both server.xml: instance 1 setuped with 9016 and instance 2
with 9017.
When I stop one of tomcats, the other is notified properly with the
following message:
12-Feb-2008 11:19:57 org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberDisappeared
INFO: Received member
disappeared:org.apache.catalina.cluster.mcast.McastMember
[tcp://127.0.0.1:9017,catalina,127.0.0.1,9017,
alive=495495]
12-Feb-2008 11:19:57 org.apache.catalina.cluster.util.FastQueue remove
INFO: FastQueue.remove: Remove aborted although queue enabled
However, if you stop one of tomcats, the sessions hanging in that tomcat,
not switch to the other,
and we need to re-execute login in the application.
This might not be relevant, but how about the data that is stored within
the session? Is the application coded so that everything that goes into
session is either serializable or transient?
--
..Juha
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
