[jira] Assigned: (JCR-233) repository lock file not removed without a clean shutdown

["Tobias Strasser (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/JCR-233?page=all ]

Tobias Strasser reassigned JCR-233:
-----------------------------------

    Assign To: Tobias Strasser

> repository lock file not removed without a clean shutdown
> ---------------------------------------------------------
>
>          Key: JCR-233
>          URL: http://issues.apache.org/jira/browse/JCR-233
>      Project: Jackrabbit
>         Type: Bug
>   Components: core
>     Reporter: fabrizio giustina
>     Assignee: Tobias Strasser
>      Fix For: 1.0
>  Attachments: replock.293087.diff
>
> actually when a repository is loaded a ".lock" file is created. This file is removed only after a clean shutdown but, if a jackrabbit instance has been killed, you have to manually delete the file in order to load the repository again, also if there was no live instance of jackrabbit that was using it.
> The problem comes from the fact that the simple presence of the .lock file is used to indicate a live instance.
> I suggest replacing this behavior using this method (used for example by eclipse when opening workspaces):
> - when an instance is loaded create a ".lock" file and open it with exclusive access
> - when a new instance is started try to delete an eventual .lock file. Only if the file can't be deleted because in use assume that another jackrabbit instance is running.

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