>I'm expecting a null from
>the following line
No, you would not expect null. The session replication mechanism is supposed to
survive context reloads.
But you should not be getting a ClassCastException, if you are I would love for you to
submit a test case.
When a context is reloaded, it will startup again, at which point the manager will
request the state from another server. This data
comes over serialized and is reloaded by the new classloader, hence you shouldn't get
ClassCastExceptions,
the only way you would get class cast exceptions is if you actually recompiled the
class on one of your servers.
Due to busy work schedule, I haven't had a chance to fix the context reload, I only
recently found out (same way you did) that
context reload was broken.
Filip
----- Original Message -----
From: "Matthew Stone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 18, 2004 2:09 PM
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
