[
https://issues.apache.org/jira/browse/JCR-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191165#comment-13191165
]
Julian Reschke commented on JCR-3215:
-------------------------------------
Well, not calling logout() can cause resources not to be freed. That's a
problem no matter whether you use remoting or not...
> not releasing session locks on session destruct
> -----------------------------------------------
>
> Key: JCR-3215
> URL: https://issues.apache.org/jira/browse/JCR-3215
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-client, locks
> Affects Versions: 2.3.6
> Reporter: David Buchmann
>
> while investigating JCR-3205 i noticed that when my client java vm terminates
> without calling explicit session.logout() the session locks are not released.
> i would expect the session to do its logout job upon destruction. from what i
> understood, the server hes no notion of session, so its the job of the client
> to clean up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
