Magnolia 5.4 reached end of life on November 15, 2018. This branch is no longer supported, see End-of-life policy.
As Magnolia currently does not provide serialization of classes for HTTP clustering, persistence of HTTP sessions is disabled by default (
Magnolia 5.4.8+) in the configuration of the Tomcat container which is bundled together with Magnolia. Disabling session persistence will remove the java.io.NotSerializableException warning from the logs. To disable the persistence in Tomcat bundled together with a previous version of Magnolia, please follow the instructions available at the apache.org website (https://tomcat.apache.org/tomcat-7.0-doc/config/manager.html#Disable_Session_Persistence).
Session persistence settings in other types of containers:
- WebLogic
Sessions are not persisted by default, cf. thepersistent-store-typeelement at https://docs.oracle.com/cd/E13222_01/wls/docs92/webapp/weblogic_xml.html. For more details see https://docs.oracle.com/cd/E13222_01/wls/docs92/webapp/sessions.html#wp139726.
- WebSphere
Go toApplication Servers > ServerName > Session Management > Distributed environment settingsand in theDistributed session propertiestab chooseNone(https://www.youtube.com/watch?v=x0Xg8RTB7T0 and http://www.ibm.com/support/knowledgecenter/SSEQTP_8.0.0/com.ibm.websphere.base.doc/info/aes/ae/tprs_cnfs.html).
Overview
Content Tools
2 Comments
Vivian Steller
Will Magnolia at some point support Session Persistence, i.e. implement Serializable correctly?
Aleksandr Pchelintcev
Hi Vivian,
I really hope that we will have session persistence in this or that form in the observable future. The biggest blocker in the past was the presence of Guice Injectors and related objects, which are not serializable by design, in http session, . Situation is better now, http sessions only contain business objects. It is still quite a task to accomplish, but at least it does not seem impossible anymore.