jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-779) Timeout for Session and/or Lock
Date Thu, 08 Mar 2007 11:38:24 GMT

     [ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-779:
------------------------------

    Component/s: locks
                 core
       Priority: Minor  (was: Critical)
     Issue Type: New Feature  (was: Improvement)

Changing the priority as it's possible for you to achieve the same functionality with extra
client code.

Session timeouts: I'm not convinced, as long as there's a reference to a Session instance
it shouldn't just be closed without explicit action from the client. Once the reference is
gone, the session should get closed as a part of the garbage collection process. I'm actually
not sure whether this happens currently. If not, please file a new bug report for that.

Lock timeouts: Again, not convinced, since session-scoped locks will expire when the associated
session is closed and open-scoped locks should by definition persist until they are explicitly
unlocked. We perhaps should provide some administrative mechanism for retrieving the lock
tokens of all active locks to avoid situations where the lock token of an open-scoped lock
gets lost, but that would again be a different feature request.

I'm inclined to resolve this issue as Won't Fix, but please counter my arguments if you think
I'm wrong.

> Timeout for Session and/or Lock
> -------------------------------
>
>                 Key: JCR-779
>                 URL: https://issues.apache.org/jira/browse/JCR-779
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: core, locks
>         Environment: All environments
>            Reporter: Sridhar
>            Priority: Minor
>
> I think there needs to be a mechanism where we can set the timeout for a particular jcr
Session.  Or at the most, there should be a provision to set a timeout for a lock on a node.
> Hope this is implemented soon.
> Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message