You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Edgar Poce (JIRA)" <ji...@apache.org> on 2005/09/09 06:02:30 UTC
[jira] Created: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
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
Assigned to: Edgar Poce
Priority: Minor
Fix For: 1.0
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Kommentiert: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-213?page=comments#action_12323015 ]
Felix Meschberger commented on JCR-213:
---------------------------------------
> 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.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Posted by "Edgar Poce (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-213?page=all ]
Edgar Poce updated JCR-213:
---------------------------
Attachment: 05-09-09-lockRepoHome.patch
I no one objects I'll apply this patch.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-213?page=comments#action_12329999 ]
Jukka Zitting commented on JCR-213:
-----------------------------------
See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4513817 for more information about the File.deleteOnExit() memory problems.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Posted by "Edgar Poce (JIRA)" <ji...@apache.org>.
[ 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-213?page=comments#action_12323002 ]
Jukka Zitting commented on JCR-213:
-----------------------------------
Sounds useful, +1 from me.
PS. Should the releaseRepositoryLock call be placed at the end of the shutdown() method instead of the beginning?
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JCR-213) Avoid creation of more than one jackrabbit instance with the same configuration
Posted by "Tobias Strasser (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-213?page=comments#action_12323011 ]
Tobias Strasser commented on JCR-213:
-------------------------------------
additionally to deleting the file explicitely, i woud also mark it for 'auto-deletion' by calling File.deleteOnExit()
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira