You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Mark Moales (JIRA)" <ji...@apache.org> on 2006/04/24 21:53:05 UTC
[jira] Created: (JCR-411) Binding repository to a nameserver with
RegistryHelper causes failure on lookup.
Binding repository to a nameserver with RegistryHelper causes failure on lookup.
--------------------------------------------------------------------------------
Key: JCR-411
URL: http://issues.apache.org/jira/browse/JCR-411
Project: Jackrabbit
Type: Bug
Components: core
Versions: 1.0
Environment: Windows XP SP2, JBoss 4.0.3SP1
Reporter: Mark Moales
Binding a repository to a nameserver using RegistryHelper causes the next subsequent lookup to fail. This is what I observerd:
1. RegistryHelper.registerRepository creates a new BindableRepository and initializes it. This, in turn, initializes the "real" repository (i.e. delagtee). It then binds this reference with the nameserver.
2. On the next lookup, BindableRepositoryFactory.getObjectInstance is invoked. Thie method checks it's cache for a repository. Since one does not exist yet, it creates a new BindableRepository and tries to initialize it. This fails since the call to RegistryHelper.registerRepository already initialized the repository.
The error message basically says the repository is already in use by another process because the .lock file is present. To fix this, I modified RegistryHelper.registerRepository to NOT initialize the repository and simply bind the "Reference".
--
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] Assigned: (JCR-411) Binding repository to a nameserver with
RegistryHelper causes failure on lookup.
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-411?page=all ]
Stefan Guggisberg reassigned JCR-411:
-------------------------------------
Assign To: Stefan Guggisberg
> Binding repository to a nameserver with RegistryHelper causes failure on lookup.
> --------------------------------------------------------------------------------
>
> Key: JCR-411
> URL: http://issues.apache.org/jira/browse/JCR-411
> Project: Jackrabbit
> Type: Bug
> Components: core
> Versions: 1.0
> Environment: Windows XP SP2, JBoss 4.0.3SP1
> Reporter: Mark Moales
> Assignee: Stefan Guggisberg
>
> Binding a repository to a nameserver using RegistryHelper causes the next subsequent lookup to fail. This is what I observerd:
> 1. RegistryHelper.registerRepository creates a new BindableRepository and initializes it. This, in turn, initializes the "real" repository (i.e. delagtee). It then binds this reference with the nameserver.
> 2. On the next lookup, BindableRepositoryFactory.getObjectInstance is invoked. Thie method checks it's cache for a repository. Since one does not exist yet, it creates a new BindableRepository and tries to initialize it. This fails since the call to RegistryHelper.registerRepository already initialized the repository.
> The error message basically says the repository is already in use by another process because the .lock file is present. To fix this, I modified RegistryHelper.registerRepository to NOT initialize the repository and simply bind the "Reference".
--
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-411) Binding repository to a nameserver with
RegistryHelper causes failure on lookup.
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-411?page=all ]
Stefan Guggisberg resolved JCR-411:
-----------------------------------
Fix Version: 1.0.1
Resolution: Fixed
fixed in svn rev. 397583
thanks for reporting this issue!
> Binding repository to a nameserver with RegistryHelper causes failure on lookup.
> --------------------------------------------------------------------------------
>
> Key: JCR-411
> URL: http://issues.apache.org/jira/browse/JCR-411
> Project: Jackrabbit
> Type: Bug
> Components: core
> Versions: 1.0
> Environment: Windows XP SP2, JBoss 4.0.3SP1
> Reporter: Mark Moales
> Assignee: Stefan Guggisberg
> Fix For: 1.0.1
>
> Binding a repository to a nameserver using RegistryHelper causes the next subsequent lookup to fail. This is what I observerd:
> 1. RegistryHelper.registerRepository creates a new BindableRepository and initializes it. This, in turn, initializes the "real" repository (i.e. delagtee). It then binds this reference with the nameserver.
> 2. On the next lookup, BindableRepositoryFactory.getObjectInstance is invoked. Thie method checks it's cache for a repository. Since one does not exist yet, it creates a new BindableRepository and tries to initialize it. This fails since the call to RegistryHelper.registerRepository already initialized the repository.
> The error message basically says the repository is already in use by another process because the .lock file is present. To fix this, I modified RegistryHelper.registerRepository to NOT initialize the repository and simply bind the "Reference".
--
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-411) Binding repository to a nameserver with
RegistryHelper causes failure on lookup.
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-411?page=comments#action_12413403 ]
Jukka Zitting commented on JCR-411:
-----------------------------------
Merged for 1.0.1 in revision 409597.
> Binding repository to a nameserver with RegistryHelper causes failure on lookup.
> --------------------------------------------------------------------------------
>
> Key: JCR-411
> URL: http://issues.apache.org/jira/browse/JCR-411
> Project: Jackrabbit
> Type: Bug
> Components: core
> Versions: 1.0
> Environment: Windows XP SP2, JBoss 4.0.3SP1
> Reporter: Mark Moales
> Assignee: Stefan Guggisberg
> Fix For: 1.0.1
>
> Binding a repository to a nameserver using RegistryHelper causes the next subsequent lookup to fail. This is what I observerd:
> 1. RegistryHelper.registerRepository creates a new BindableRepository and initializes it. This, in turn, initializes the "real" repository (i.e. delagtee). It then binds this reference with the nameserver.
> 2. On the next lookup, BindableRepositoryFactory.getObjectInstance is invoked. Thie method checks it's cache for a repository. Since one does not exist yet, it creates a new BindableRepository and tries to initialize it. This fails since the call to RegistryHelper.registerRepository already initialized the repository.
> The error message basically says the repository is already in use by another process because the .lock file is present. To fix this, I modified RegistryHelper.registerRepository to NOT initialize the repository and simply bind the "Reference".
--
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