Hi,
Because I'm running neo4j in OSGI with eclipse, the bundle
neo4j.lucene-index requires an OSGI lucene bundle to resolve constraint, so
I can't simply put lucene-core-3.2.0.jar into my java class path, I tried to
put lucene into a bundle and export all package for other bundles, but it
seems not work for me.
On Wed, Jun 8, 2011 at 13:24, David Montag
<david.mon...@neotechnology.com>wrote:
> Hi,
>
> Can you please confirm that you have the lucene index JAR file on the
> classpath?
>
> Thanks,
> David
>
> On Tue, Jun 7, 2011 at 10:10 PM, Super Wang <wangxu...@gmail.com> wrote:
>
> > There's same error in 1.4.M03 or 1.4.SNAPSHOT too:
> >
> > Root exception:
> > java.lang.IllegalArgumentException: No index provider 'lucene' found
> > at
> >
> >
> org.neo4j.kernel.IndexManagerImpl.getIndexProvider(IndexManagerImpl.java:69)
> > at
> >
> >
> org.neo4j.kernel.IndexManagerImpl.findIndexConfig(IndexManagerImpl.java:109)
> > at
> >
> >
> org.neo4j.kernel.IndexManagerImpl.getOrCreateIndexConfig(IndexManagerImpl.java:171)
> > at org.neo4j.kernel.IndexManagerImpl.forNodes(IndexManagerImpl.java:242)
> > at com.isocialcloud.db.model.UserRepository.init(UserRepository.java:29)
> > at
> >
> >
> com.isocialcloud.db.model.UserRepository.bindService(UserRepository.java:62)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:360)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:423)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:211)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:337)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
> > at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
> > at
> >
> >
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
> > at
> >
> >
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:933)
> > at
> >
> >
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
> > at
> >
> >
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
> > at
> >
> >
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:756)
> > at
> >
> >
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:711)
> > at
> >
> >
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> > at
> >
> >
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
> > at
> >
> >
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:507)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:504)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:259)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
> > at
> >
> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
> > at
> >
> >
> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
> > at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
> > at
> >
> >
> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
> >
> > On Fri, Jun 3, 2011 at 16:24, Mattias Persson <matt...@neotechnology.com
> > >wrote:
> >
> > > Hi John,
> > >
> > > it's a known issue and have been fixed in 1.4.M03. Please try out that
> > > version instead.
> > >
> > > Best,
> > > Mattias
> > >
> > > 2011/6/2, John Howard <johnyho...@gmail.com>:
> > > > Hello,
> > > >
> > > > We have been consistently getting the following exception from neo4j
> > > index.
> > > > java.lang.IllegalArgumentException: Illegal Capacity: -11
> > > > at java.util.ArrayList.<init>(ArrayList.java:110)
> > > > at
> org.neo4j.index.impl.lucene.LuceneIndex.query(LuceneIndex.java:271)
> > > > at org.neo4j.index.impl.lucene.LuceneIndex.get(LuceneIndex.java:187)
> > > > at strategic.poc.NeoSearch.getNodes(NeoSearch.java:250)
> > > >
> > > > Scenario:
> > > > We are trying to update Nodes by creating new relationships. Before
> we
> > > > create a new relationship, we find the existing node by key/value.
> > > > If we update less than say 20 nodes(ie, create one new relationship
> to
> > > each
> > > > node), there's no problem.
> > > > However if we update say 25 or 30 or 50 nodes, we get the above
> > > exceptions
> > > > when we try to lookup for a node based on key/value.
> > > >
> > > > Here's the code which does the lookup in the index to find a node:
> > > >
> > > > public IndexHits getNodes(String key, String value)
> > > > {
> > > > Index index = graphDb.index().forNodes( "testIndex" );
> > > > value = value.toLowerCase();
> > > > return index.get(key, value); // line# 250
> > > >
> > > > }
> > > >
> > > > we are using neo4j1.4-M02 binaries, standalone version.
> > > > By the way, we are able to create almost 5000 new nodes in one
> > > > transacwithout any problem. We dont do lookups when creating a new
> > node.
> > > > It's only when updating it breaks.
> > > >
> > > > Is something wrong with the way we are searching or is it a bug in
> > > > LuceneIndex?
> > > > Is there a workaround?
> > > >
> > > >
> > > > Thank you.
> > > >
> > > > John
> > > > _______________________________________________
> > > > Neo4j mailing list
> > > > User@lists.neo4j.org
> > > > https://lists.neo4j.org/mailman/listinfo/user
> > > >
> > >
> > >
> > > --
> > > Mattias Persson, [matt...@neotechnology.com]
> > > Hacker, Neo Technology
> > > www.neotechnology.com
> > > _______________________________________________
> > > Neo4j mailing list
> > > User@lists.neo4j.org
> > > https://lists.neo4j.org/mailman/listinfo/user
> > >
> > _______________________________________________
> > Neo4j mailing list
> > User@lists.neo4j.org
> > https://lists.neo4j.org/mailman/listinfo/user
> >
>
>
>
> --
> David Montag <david.mon...@neotechnology.com>
> Neo Technology, www.neotechnology.com
> Cell: 650.556.4411
> Skype: ddmontag
> _______________________________________________
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
