[dna-issues] [JBoss JIRA] Updated: (DNA-541) Locking Implementation Does Not Support Timeouts

Brian Carothers (JIRA) jira-events at lists.jboss.org
Sun Dec 6 11:01:29 EST 2009


     [ https://jira.jboss.org/jira/browse/DNA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-541:
--------------------------------

    Attachment: DNA-541_admin_unlock.patch


Those are good calls.

Attached is a patch that implements lock expiration based on the algorithm above modified by Randall's comments.  The patch includes two tests to confirm that the functionality works, but one is @Ignored because it depends on garbage collector behavior to test the results and the other is @Ignored because it has to sleep for 30 seconds to test the timeout.

If the patch looks ok, I will commit it and resolve the defect.

> Locking Implementation Does Not Support Timeouts
> ------------------------------------------------
>
>                 Key: DNA-541
>                 URL: https://jira.jboss.org/jira/browse/DNA-541
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_admin_unlock.patch
>
>
> The locking implementation does not provide a means of expiring stale or old locks (other than having the original owner unlock them).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the dna-issues mailing list