[ http://jira.magnolia.info/browse/MAGNOLIA-765?page=all ]
Sameer Charles resolved MAGNOLIA-765.
-------------------------------------
Resolution: Fixed
done
- All objects associated to HttpSession are searializable
- WorkspaceAccessUtil replaces SessionStore providing all magnolia specific
objects needed to accees JCR
> session must be serializable (session clustering failing)
> ---------------------------------------------------------
>
> Key: MAGNOLIA-765
> URL: http://jira.magnolia.info/browse/MAGNOLIA-765
> Project: Magnolia
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0 Beta 1
> Environment: Any (linux, java 6)
> Reporter: Nicolas Modrzyk
> Assigned To: Sameer Charles
> Priority: Blocker
> Fix For: 3.1
>
>
> I put in the magnoliaAuthor war into webapps
> Then added <distributed /> to the Author webapps to enable clustering/session
> failover
> Also uncommented the Cluster setting as well.
> I tried connecting to one of the Tomcat instances directly to double check
> things are working
> And found I could not connect to the Magnolia author at all
> In catalina.out there is the following message:
> ERROR info.magnolia.cms.filters.SecurityFilter
> SecurityFilter.java(authenticate:120) 14.03.2006 16:28:39 Attribute
> [mgnlUserNode] is not serializable
> java.lang.IllegalArgumentException: Attribute [mgnlUserNode] is not
> serializable
> at
> org.apache.catalina.cluster.session.DeltaSession.setAttribute(DeltaSession.java:1229)
> at org.apache.catalina.cluster.session.DeltaSession.setAttribute() ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------