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]
