The 5.7 branch of Magnolia reached End-of-Life on December 31, 2023, as specified in our End-of-life policy. This means the 5.7 branch is no longer maintained or supported. Please upgrade to the latest Magnolia release. By upgrading, you will get the latest release of Magnolia featuring significant improvements to the author and developer experience. For a successful upgrade, please consult our Magnolia 6.2 documentation. If you need help, please contact info@magnolia-cms.com.
As Magnolia currently does not provide serialization of classes for HTTP clustering, persistence of HTTP sessions is disabled by default 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