Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
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:
Sessions are not persisted by default, cf. the
persistent-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.
Application Servers > ServerName > Session Management > Distributed environment settingsand in the
Distributed session propertiestab choose
None(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).