4.3.1. Session leak detector

Warning

You are looking at documentation for an older release. Not what you want? See the current release documentation.

The session leak detector is able to help you debug your application based on JCR when you suspect that you have a bug related to a wrong usage of JCR sessions. It works by creating a queue of weak references to JCR sessions and the queue is periodically cleaned. When a session reference is dequeued and is not cleared it is considered as a leaked session. Obviously what matters here is the time by which a session is stale known as max age. If the max age is too short, it will suspect that many sessions are leaked although they are not. The default max age value is configured at 2 minutes.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus