Return-Path: 
 <dev-return-27732-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
Received: (qmail 89128 invoked from network); 18 Mar 2010 10:36:55 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 18 Mar 2010 10:36:55 -0000
Received: (qmail 94310 invoked by uid 500); 18 Mar 2010 10:36:55 -0000
Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
Received: (qmail 94066 invoked by uid 500); 18 Mar 2010 10:36:52 -0000
Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:dev@jackrabbit.apache.org>
List-Id: <dev.jackrabbit.apache.org>
Reply-To: dev@jackrabbit.apache.org
Delivered-To: mailing list dev@jackrabbit.apache.org
Received: (qmail 94059 invoked by uid 99); 18 Mar 2010 10:36:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Mar 2010 10:36:51 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Mar 2010 10:36:48 +0000
Received: from brutus.apache.org (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 5373B234C4B1
	for <dev@jackrabbit.apache.org>; Thu, 18 Mar 2010 10:36:27 +0000 (UTC)
Message-ID: <1581953125.338691268908587340.JavaMail.jira@brutus.apache.org>
Date: Thu, 18 Mar 2010 10:36:27 +0000 (UTC)
From: "Thomas Mueller (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2450) UserManager inconsistency
In-Reply-To: <1480322607.43951262700654435.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/JCR-2450?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128468=
29#action_12846829 ]=20

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=3D"default">
<FileSystem class=3D"org.apache.jackrabbit.core.fs.local.LocalFileSystem">
        <param name=3D"path" value=3D"${wsp.home}" />
</FileSystem>
<PersistenceManager
        class=3D"org.apache.jackrabbit.core.persistence.bundle.MySqlPersist=
enceManager">
        <param name=3D"url" value=3D"jdbc:mysql://localhost:3306/jackrabbit=
_test" />
        <param name=3D"user" value=3D"jack" />
        <param name=3D"password" value=3D"test" />
        <param name=3D"schema" value=3D"mysql" />
        <param name=3D"schemaObjectPrefix" value=3D"pm_jackrabbit_" />
</PersistenceManager>
<SearchIndex class=3D"org.apache.jackrabbit.core.query.lucene.SearchIndex">
        <param name=3D"path" value=3D"${wsp.home}/index" />
       ...
</SearchIndex>
</Workspace>

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

<param name=3D"schemaObjectPrefix" value=3D"${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=C3=A4mpfli
>            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 w=
ith 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 conn=
ection 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 agai=
n (using WebDAV), I see that the user node moved to the root node. As a con=
sequence the user cannot login to the repository because the user manager c=
annot find the user node anymore.
> In jackrabbit 2.0-beta4 I get a similar bug and I assume, that the root c=
ause is the same as above. I log into the repository using the administrato=
r account, which is created automatically with the class UserManagerImpl. W=
hen I restart Tomcat and try to login to the repository I get the error: ja=
vax.jcr.ItemNotFoundException: failed to build path of 55411ff4-d6c7-410a-a=
16e-5531e1c7afae: cafebabe-cafe-babe-cafe-babecafebabe has no child entry f=
or 55411ff4-d6c7-410a-a16e-5531e1c7afae

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