Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of tranier@gmail.com designates
 209.85.214.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=o6M+3pJF2QiMBFHgFrOwwqvaf+cUTlsK5ykd0Ms9YMdQiFtuvqbUJsk515j8zlxD33
         EXsWz+/8uOZlH0AL+v0dqylNkpfAVf3rebPp46wJnUdNKznEY93/rwzgpJWVus2Iedvu
         zWW1HTDVN11ePGrOyekeBMnOAhPYQfIgwimsw=
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Disable lucene in jackrabbit
From: John Tranier <tranier@gmail.com>
In-Reply-To: <AANLkTi=DpJMpFC8xVo8mzxSgis_ZA_nGB9u8UfFw1r9n@mail.gmail.com>
Date: Mon, 14 Feb 2011 20:37:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7AECEE7-86F4-4FDA-9723-B9AD6BDA21E2@gmail.com>
References: <4D53F79B.2080203@maisis.pt> <C979B7D4.AEBF%mueller@adobe.com>
 <AANLkTi=DpJMpFC8xVo8mzxSgis_ZA_nGB9u8UfFw1r9n@mail.gmail.com>
To: users@jackrabbit.apache.org

Hi,

I had the same experience : comment out the searchIndex section leads to =
errors in the log.
I asked about it on the list, and I've been told the kernel uses the =
searchIndex to support its internal queries.
So I'm a bit confused about the last update of documentation.

We've faced a severe issue on our application using Jackrabbit as =
repository : users was complaining about random lost of documents.
We did several actions, including reactivation of the searchIndex, and =
the problem disappeared.=20
I cannot tell for sure if the searchIndex was the the cause of the =
problem, but I'm not very likely to disable it now.=20

Regards,
John


Le 14 f=E9vr. 2011 =E0 05:49, Kevin Jansz a =E9crit :

> with SearchIndex commented out I've found you get the following logged
> as "ERROR" when logging in:
>=20
> ERROR [main] [14 Feb 2011 15:40:58,693
> =
org.apache.jackrabbit.core.security.user.AuthorizableImpl:getMembershipRef=
erences@371]:
> Failed to retrieve membership references of User 'admin'.
> javax.jcr.RepositoryException: Unable to retrieve WEAKREFERENCE
> properties that refer to 21232f29-7a57-35a7-8389-4a0e4a801fc3
> 	at =
org.apache.jackrabbit.core.NodeImpl.getWeakReferences(NodeImpl.java:3461)
> 	at =
org.apache.jackrabbit.core.security.user.AuthorizableImpl.getMembershipRef=
erences(AuthorizableImpl.java:369)
> 	at =
org.apache.jackrabbit.core.security.user.AuthorizableImpl.collectMembershi=
p(AuthorizableImpl.java:312)
> 	at =
org.apache.jackrabbit.core.security.user.AuthorizableImpl.memberOf(Authori=
zableImpl.java:100)
> 	at =
org.apache.jackrabbit.core.security.user.UserImpl.memberOf(UserImpl.java:3=
6)
> 	at =
org.apache.jackrabbit.core.security.principal.DefaultPrincipalProvider.col=
lectGroupMembership(DefaultPrincipalProvider.java:290)
> 	at =
org.apache.jackrabbit.core.security.principal.DefaultPrincipalProvider.get=
GroupMembership(DefaultPrincipalProvider.java:194)
> 	at =
org.apache.jackrabbit.core.security.authentication.AbstractLoginModule.get=
Principals(AbstractLoginModule.java:676)
> 	at =
org.apache.jackrabbit.core.security.authentication.AbstractLoginModule.com=
mit(AbstractLoginModule.java:369)
> 	at =
org.apache.jackrabbit.core.security.authentication.LocalAuthContext.login(=
LocalAuthContext.java:86)
> 	at =
org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1497)
>        ...
> Caused by: javax.jcr.RepositoryException: no search manager configured
> for this workspace
> 	at =
org.apache.jackrabbit.core.WorkspaceImpl.getQueryManager(WorkspaceImpl.jav=
a:778)
> 	at =
org.apache.jackrabbit.core.NodeImpl.getWeakReferences(NodeImpl.java:3445)
> 	... 33 more
>=20
>=20
> This is in jackrabbit 2.1.0, possibly to do with the "Default"
> security config in place:
>    <Security appName=3D"Jackrabbit">
>        <SecurityManager
> class=3D"org.apache.jackrabbit.core.DefaultSecurityManager"
> workspaceName=3D"security"/>
>        <AccessManager
> class=3D"org.apache.jackrabbit.core.security.DefaultAccessManager"/>
>        <LoginModule
> class=3D"org.apache.jackrabbit.core.security.simple.SimpleLoginModule">
>           <param name=3D"anonymousId" value=3D"anonymous"/>
>           <param name=3D"adminId" value=3D"admin"/>
>        </LoginModule>
>    </Security>
>=20
> ... because there's no alternative QueryManager when no (lucene)
> SearchIndexes are configured? It doesn't seem to stop the repository
> from responding
>=20
> --
> Kevin Jansz
> kevin.jansz@exari.com
> Level 7, 10-16 Queen Street, Melbourne 3000 Australia
> Tel +61 3 9621 2773 | Fax +61 3 9621 2776
> Exari Systems
> Boston | London | Melbourne | Munich
> www.exari.com
>=20
> Test drive our software online - www.exari.com/demo-trial.html
> Read our blog on document assembly - blog.exari.com
>=20
>=20
>=20
>=20
> On 11 February 2011 01:43, Thomas Mueller <mueller@adobe.com> wrote:
>> Hi,
>>=20
>> I have updated the documentation at:
>> http://wiki.apache.org/jackrabbit/Search#Search_Configuration
>>=20
>>=20
>> "To disable the search index, disable (comment out) the index
>> configuration in the file repository.xml and workspace.xml file(s)."
>>=20
>> Regards,
>> Thomas
>>=20
>>=20
>> On 2/10/11 3:35 PM, "Pedro Saraiva" <psaraiva@maisis.pt> wrote:
>>=20
>>> Hello,
>>>=20
>>> It's possible to disable the lucene indexing/searching in =
jackrabbit?
>>>=20
>>> Kind regards,
>>>=20
>>> Pedro Saraiva
>>=20
>>=20