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.
HTTP and JCR session debugging.
HTTP session debugging
For HTTP session related issues, check:
- The contents of the sessions
- When the sessions are created
- What attributes are added/removed
Magnolia provides a basic
SessionDebugger class to assist with this process. The
SessionDebugger class is both a
javax.servlet.Filter and an
HttpSessionListener. To enable the filter, register it in Magnolia's filter chain. To enable the session event listener, add the following to your web.xml:
<listener> <listener-class>info.magnolia.debug.SessionDebugger</listener-class> </listener>
This listener logs a large quantity of data in WARN mode. Be sure to disable this process when the debugging session is over.
JCR session monitoring
Magnolia includes a simple JMX Mbean which allows you monitor currently opened JCR sessions. Connect to your container (for instance using JConsole) and locate the
Magnolia JCRStats MBean. It will show you how many JCR sessions are currently open. See Monitoring for more.