[
https://issues.apache.org/jira/browse/JCR-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Belrose updated JCR-2868:
-----------------------------------
Attachment: repository.xml
quantel.txt
DBBug.java
> A failure to connect to a MySQL database when JackRabbit starts a session
> leaves a .lock file in the repository. Subsequent sessions cannot be created
> by the same thread.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-2868
> URL: https://issues.apache.org/jira/browse/JCR-2868
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.2.0
> Environment: Windows XP, Java version 1.6.0_21, MySQL 5.1.48
> Reporter: Guillaume Belrose
> Attachments: DBBug.java, quantel.txt, repository.xml
>
>
> I investigating the robustness of JackRabbit in the face of unexpected
> database errors, such as the database being unavailable. In my particular
> case, I am attempting to start a JackRabbit session using a
> TransientRepository while the database is not yet running. This correctly
> fails. However, if I attempt to create another session within the same thread
> after a short while, an exception occurs saying that the repository has
> already been locked. I would expect the repository folder not to be locked.
> Maybe the code meant to remove the .lock file was not triggered because of an
> uncaught exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
