[
https://issues.apache.org/jira/browse/JCR-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Micah Whitacre updated JCR-1318:
--------------------------------
Attachment: JCR_1318-patch.txt
I created a patch based on the 1.3 branch of jackrabbit-core that isn't
necessarily pretty but does at least make the testcase i provided repeatedly
generate the same stack trace for attempts to create an instance of
RepositoryImpl. This could probably be simplified a bit if the shutdown()
method was a little bit more tolerant of everything not necessarily being
initialized by that point.
> 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
> 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.
