Hi,
yes I already did know what this parameter means (though I only realised it after reading the source code ;), so the behaviour I described makes probably sense in this context.
But my concern is the following:
If a cluster completely fails, i.e. all nodes on the cluster crash (which is not so unlikely with small 2-3 node clusters), the session data is completely lost even if I can restart all nodes immediately.
In our case we have a cluster of just 2 nodes and we want to use a tomcat session replication (among other points) to be able to update the webapps without killing all user session on a node. So we would first stop Tomcat A, update its webapp, restart tomcat A and then the same for Tomcat B. If Tomcat B would now die while Tomcat A is down all session information would be lost.
I wanted to know if there is a way to handle this kind of situation.
TIA Christoph
PS: do you have any information regarding point b?
Filip Hanik - Dev wrote:
expireSessionsOnShutdown="false" -> on shutdown -> expire sessions locally, but do not propagate to the cluster expireSessionsOnShutdown="true" -> on shutdown -> expire sessions locally, and propagate to the cluster stupid name for the variable, I agree
----- Original Message ----- From: "Christoph Kutzinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 09, 2004 8:00 AM
Subject: Session expiry and SessionListener problems with cluster
Hi,
I'm just "playing" with the Tomcat 5.5.4 cluster and encountered 2 oddities:
a) If have left expireSessionsOnShutdown="false" in the configuration
I understand that this will expire the session in the local node but leave it alive in the other cluster nodes.
However I found out that the session will expire in the local node on shutdown even if there are no other nodes in the cluster. So the session will be lost after restart.
Is this expected behaviour or a bug?
b) I implemented a session listerner for attributes.
I noticed that the attributeAdded event from DeltaManager always return null as the value of the event where the normal session manager will return the value of the attribute added. Sourcecode:
public void attributeAdded(HttpSessionBindingEvent evt) { // == null with DeltaManager, != null otherwise Object value = evt.getValue(); // != null in both cases Object value1 = evt.getSession().getAttribute(evt.getName()); }
Is this a bug?
Thanks in advance,
Christoph
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
