Matt, No other nodes are up, so there's nothing to serialize. I could imagine that the session of the old context could be serialized to the new context in order to preserve state, although I hope this isn't done.
Thanks, Matthew "Dale, Matt" wrote: > Surely when you restart the context all the sessions will get serialised then > reloaded so I would expect this behaviour. You would have to set the cluster to dump > sessions on a reload. > > -----Original Message----- > From: Matthew Stone [mailto:[EMAIL PROTECTED] > Sent: 18 October 2004 20:09 > To: [EMAIL PROTECTED] > Subject: Session problems with cluster > > When I restart the context of a clustered node the session doesnt seem > to be cleared. After I restart the context, I'm expecting a null from > the following line but I'm getting a ClassCastException because of the > different class loaders that loaded MyObject. > > MyObject obj = (MyObject) request.getSession ().getAttribute > ("my_object"); > > I'm using 5.0.25 because I was running into bug 31495 "Context reload > causes ClusterManager to stop operating" in version 5.0.28. > > Does 5.0.29 address this? I didn't see that the bug was closed. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ------------------------------------------------------------------------ > Name: InterScan_Disclaimer.txt > InterScan_Disclaimer.txt Type: Plain Text (text/plain) > Encoding: 7bit > > ------------------------------------------------------------------------ > --------------------------------------------------------------------- > 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]
