Marc, Could you check if the node that you invoke getSingleRelationship on actually has one relationship (of BELONGS_TO_CATEGORY, OUTGOING) when you only perform read operations. You could use the shell (see http://wiki.neo4j.org/content/Shell) and go to the node listing all relationships:
// go to node 149816 and list relationships neo-sh (0)$ cd -a 149816 neo-sh (0)$ ls -Johan On Sat, Oct 10, 2009 at 4:35 PM, Marc Preddie <mpred...@gmail.com> wrote: > Hi Johan, > No, I am strictly reading from the graph. I have single read only instance > which I am attempting to use across multiple threads as you suggest. > > Regards, > Marc > > On Sat, Oct 10, 2009 at 9:23 AM, Johan Svensson > <jo...@neotechnology.com>wrote: > >> 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
