Hi, On Mon, Oct 4, 2010 at 10:59 AM, Narendra Sharma <[email protected]> wrote: > 1. What does this exception mean?
This warnings is logged when the JVM reclaims an unreferenced Session as garbage. It signals a code path that opens a new session but then forgets to properly close once the session is no longer used. The included stack trace is meant to help locate the troublesome code path. > 2. Is it harmful? Jackrabbit will automatically close the stray session in such cases, so the only real harm done is that the unclosed session has unnecessarily tied up system resources that could have been released already before. > 3. Can this result in abrupt session close and operation failure? No. The session is only automatically closed once the JVM reclaims it as garbage, i.e. once there are no other references to the session. > 4. What triggers this exception? Garbage collection. > 5. I use a Session cache which holds and reuses session for same user > operations. Two different users don't share the same session. The session > may be live for long duration (few minutes) if user keep performing > operations. Could this use case result into this exception? Only if your Session cache leaks. BR, Jukka Zitting
