jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edgar Poce (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Date Fri, 09 Sep 2005 13:31:31 GMT
     [ http://issues.apache.org/jira/browse/JCR-213?page=all ]
Edgar Poce resolved JCR-213:

    Resolution: Fixed

> > i woud also mark it for 'auto-deletion' by calling File.deleteOnExit()
> I would not. Apart from deleteOnExit() being prone to memory problems, 
> I think the existence of the lock file beyond the life time of the repository would 
> indicate problems.

I agree with felix. anyway the change proposed by tobi can be added later if needed.

> PS. Should the releaseRepositoryLock call be placed at the end of the shutdown() method

> instead of the beginning?

I agree. 

thanks for your comments

> Avoid creation of more than one jackrabbit instance with the same configuration
> -------------------------------------------------------------------------------
>          Key: JCR-213
>          URL: http://issues.apache.org/jira/browse/JCR-213
>      Project: Jackrabbit
>         Type: Improvement
>   Components: core
>     Reporter: Edgar Poce
>     Assignee: Edgar Poce
>     Priority: Minor
>      Fix For: 1.0
>  Attachments: 05-09-09-lockRepoHome.patch
> based on the mailing list archive, it seems new users often run more than one jackrabbit
instance with the same configuration. I propose to lock the repository by creating an empty
file called ".lock" at the repository home on startup and remove it on shutdown.
> If the lock file is found on jackrabbit startup the following message will be logged:
> "The repository home at " + home.getAbsolutePath() + " appears to be in use. If you are
sure it's not in use please delete the file at  " + lock.getAbsolutePath() + ". Probably the
repository was not shutdown properly."

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