jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-411) Binding repository to a nameserver with RegistryHelper causes failure on lookup.
Date Thu, 27 Apr 2006 16:23:38 GMT
     [ 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:
For more information on JIRA, see:

View raw message