[ 
https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846829#action_12846829
 ] 

Thomas Mueller commented on JCR-2450:
-------------------------------------

This looks like a repository configuration problem. In your test case there is 
a repository.xml file which contains:

<Workspace name="default">
<FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
        <param name="path" value="${wsp.home}" />
</FileSystem>
<PersistenceManager
        
class="org.apache.jackrabbit.core.persistence.bundle.MySqlPersistenceManager">
        <param name="url" value="jdbc:mysql://localhost:3306/jackrabbit_test" />
        <param name="user" value="jack" />
        <param name="password" value="test" />
        <param name="schema" value="mysql" />
        <param name="schemaObjectPrefix" value="pm_jackrabbit_" />
</PersistenceManager>
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
        <param name="path" value="${wsp.home}/index" />
       ...
</SearchIndex>
</Workspace>

That means it will use a different file system path and search index for each 
workspace (${wsp.home}), but it will use the same database, schema prefix, and 
table for all workspaces. I suggest to use something like:

<param name="schemaObjectPrefix" value="${wsp.name}_"/>


> UserManager inconsistency
> -------------------------
>
>                 Key: JCR-2450
>                 URL: https://issues.apache.org/jira/browse/JCR-2450
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, security
>    Affects Versions: 1.6.0, 2.0-beta4
>         Environment: Ubuntu 9.04 64bit, Tomcat 6.0.20, Jackrabbit 1.6 and 
> 2.0-beta4
>            Reporter: Michael Stämpfli
>            Priority: Blocker
>         Attachments: jackrabbit-test.zip
>
>
> I used the default class UserManagerImpl to add a user to my jackrabbit (1.6) 
> environment. My application can successfully login to the repository with 
> this user. As soon as I restart Tomcat, the login fails.
> I did some research and found out why. Obviously the user manager cannot find 
> the user, I registered previously, anymore. Using WebDAV I made a connection 
> to the security workspace. When I create a new user, a new node for this user 
> is created in /jcr:root/rep:security/rep:authorizables/rep:users/admin. As 
> soon as I restart Tomcat and login to the security workspace again (using 
> WebDAV), I see that the user node moved to the root node. As a consequence 
> the user cannot login to the repository because the user manager cannot find 
> the user node anymore.
> In jackrabbit 2.0-beta4 I get a similar bug and I assume, that the root cause 
> is the same as above. I log into the repository using the administrator 
> account, which is created automatically with the class UserManagerImpl. When 
> I restart Tomcat and try to login to the repository I get the error: 
> javax.jcr.ItemNotFoundException: failed to build path of 
> 55411ff4-d6c7-410a-a16e-5531e1c7afae: cafebabe-cafe-babe-cafe-babecafebabe 
> has no child entry for 55411ff4-d6c7-410a-a16e-5531e1c7afae

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to