Hi, Do you have a NeoService writing to the store concurrently with the embedded read only ones?
Regarding the other question you should use one NeoService (instance) per machine/across multiple threads. The read only instance is more suitable when your graph does not change and you need to load balance reads over multiple machines. Regards, -Johan On Thu, Oct 8, 2009 at 11:52 PM, Marc Preddie <mpred...@gmail.com> wrote: > Hi, > When using multiple threads if I use normal (non readonly) neo and lucene > index everything works perfectly. If I use the readonly versions of neo and > luceneIndex; I begin to get errors of the sort > --- > More than one relationship[BELONGS_TO_CATEGORY, OUTGOING] found for > NodeImpl#149816 > --- > from ... NodeImpl.getSingleRelationship. If I use the readonly versions from > a single thread everything works. > > Has anyone come across this issue? I'm using build 3108. > > One other question I have is would it better to use a readonly neo/index > instance per thread or use a single neo/index across multiple threads? > > Regards, > Marc _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
