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

Jukka Zitting resolved JCR-2868.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.3
         Assignee: Jukka Zitting

Thanks for the detailed report! I fixed this in revision 1066071 by making sure 
that the repository lock gets removed even if all else (including automatic 
shutdown that's attempted in this case) fails. Merged to the 2.2 branch in 
revision 1066072.

> 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
>            Assignee: Jukka Zitting
>             Fix For: 2.2.3
>
>         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.
> Please see the attached files:
> -a test class to reproduce the problem
> -my repository.xml config
> -the log file quantel.txt with details about the stack trace.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to