Mark's assessment is correct, how did you end up storing your request
object in the session?
Mark Hagger wrote:
My best guess is that you've somehow stored the request object itself on
the session, and thus the replication is trying to replicate that to the
other nodes.
If this is the case
My best guess is that you've somehow stored the request object itself on
the session, and thus the replication is trying to replicate that to the
other nodes.
If this is the case then this is almost certainly a bad idea.
Mark
On Thu, 2006-08-24 at 09:04 -0500, Bischoff, Mathew wrote:
> Hi,
>
Hi,
I'm starting to get clustering running on Tomcat I think I've solved
most of my webapp's non-serialized object issues, but now I'm getting
the error below. From what I can see , the error is not originating from
my code in the webapp, and searching the web for this error message
hasn't turned
