You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2008/01/18 14:55:34 UTC

[jira] Resolved: (JCR-1318) Repository Home locked not released despite RepositoryException being thrown.

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

Stefan Guggisberg resolved JCR-1318.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.4

fixed in svn r613160.

micah, thanks for reporting this issue and providing a test case incl. patch!
WRT your patch: i've chosen a slightly different approach (that you also 
mentioned in your comment).



> Repository Home locked not released despite RepositoryException being thrown.
> -----------------------------------------------------------------------------
>
>                 Key: JCR-1318
>                 URL: https://issues.apache.org/jira/browse/JCR-1318
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.3.3
>         Environment: windows vista  jdk 5
>            Reporter: Micah Whitacre
>            Assignee: Stefan Guggisberg
>             Fix For: 1.3.4
>
>         Attachments: JCR_1318-patch.txt, JCR_1318_tests.zip
>
>
> When an exception is thrown when calling RepositoryImpl.create(...) a .lock file is created in the repository home directory and not removed despite there no longer being an active connection.  If the user attempts to create the repository again (e.g recover from the exception because the url of the repository was temporarily unavailable) a RepositoryException is thrown again indicating that the repository home is locked by another process because there is a .lock file.  If a Repository is not successfully created then the repository home should not be locked.
> The lock is only released when the repository is shutdown but in this case the Repository object is never created successfully for that method to be called.

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