problem solved - using Tomcat5.0 instead of 4.1 does the trick...
katrin
Joerg Heinicke <[EMAIL PROTECTED]>
01.06.2004 22:09
Please respond to users
To: [EMAIL PROTECTED]
cc:
Subject: Re: Authentication Framework / NotSerializableException
On 01.06.2004 15:37, [EMAIL PROTECTED] wrote:
> Hello,
> I'm using the authentication framework (very basically, I believe) and
get
> a notSerializableException when stopping the server while a session
> exists.
> The environment is JBoss3.2.3 with embedded Tomcat4.1 and cocoon2.1.3.
> I have looked for information for several hours now but don't seem to
find
> anything.
> I'd appreciate any hints on what I'm doing wrong here...
>
>
> 14:37:54,234 ERROR [Engine] StandardManager[/cocoon] Cannot serialize
> session attribute
>
org.apache.cocoon.webapps.authentication.components.DefaultAuthenticationManager/UserStatus
> for session E6B9B711B490C566CD6A902677CDBF11
> java.io.NotSerializableException:
> org.apache.cocoon.components.ComponentContext
You have an object in the session that is tried to be persisted (written
to persistent store on disk) but it fails obviously. The question is of
course why the session will be persisted at all. Is it a feature of
JBoss/Tomcat with an option to deactivate it or just default behaviour
(what I can't imagine because you are not the only one having objects in
the session that are not Serializable).
Joerg
---------------------------------------------------------------------
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]
