jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-233) repository lock file not removed without a clean shutdown
Date Mon, 03 Oct 2005 07:43:48 GMT
    [ http://issues.apache.org/jira/browse/JCR-233?page=comments#action_12331137 ] 

Marcel Reutegger commented on JCR-233:

I also like the approach to use an exclusive file lock.

As a consequence it seems that creating and removing the .lock file is of no use anymore,
because it does not actually indicate whether an instance is really using the lock file. The
primary indicator is the presence on an exclusive lock on a well known file.

So, how about initially creating the lock file if it is not there and then use only file locking
to prevent multiple instances running on the same repository data?

> 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
>     Versions: 1.0
>     Reporter: fabrizio giustina

> 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:
For more information on JIRA, see:

View raw message