Hi Raul, Thanks for spotting this bug, not many people have.
This is a cache bug that was found and fixed a while back (10 days or so). There has not been a new release since then, so if you are not running on the version from trunk that would explain it. If however you are running on the version in trunk that would mean that there are other causes of this problem that we have not found yet. So I guess my followup question to you is: Which version of Neo4j are you running? The video you sent is still interesting (you don't have to send it to me) I'll watch it with Peter when he gets into the office this morning. To answer another question you had: yes, it does make sense to be able to have multiple relationships of the same type with the same source node and target node, in the case of this bug however you end up with two copies (in the in-memory cache, not on disk) of the exact same relationship. Cheers, Tobias On Thu, Feb 4, 2010 at 12:18 AM, Raul Raja Martinez <[email protected]>wrote: > Here is a attached a video that shows a similar or the same problem. > > Calling getSingleRelationship results in a exception but after > inspecting the variables call the relationships with that same type > have the have the same relationship id. > > Does it make sense to have a two relationships of the same type > attached to the same node with the same id? or is this a bug? > > 2010/2/3 Raul Raja Martinez <[email protected]>: > > ...ThreadPoolTaskExecutor#7ec48b77-42 02/03 exception: class > > org.neo4j.api.core.NotFoundException : More than one > > relationship[DynamicRelationshipType[profile], OUTGOING] found for > > NodeImpl#56493... > > > > Strange behavior when calling getSingleRelationship > > > > This is a strange "bug" or some issue we're finding when running in > > separate threads. > > In some cases this exception is thrown even when the node has a single > > relationship after placing a debug point. > > In other cases after inspecting the node the is in fact two > > relationships of the same type pointing to the same end node but > > different node proxy instances. > > Has anybody seen anything similar? We assumed Nodes and their > > operations are thread safe so we have no particular synchronization > > around creating relationships. > > We have not been able to create a test case for this issue besides > > putting a debug point on that exception and let it run on thousands of > > records for a while with operations managed by a thread-pool. > > > > > > -- > Raul Raja > > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > > -- Tobias Ivarsson <[email protected]> Hacker, Neo Technology www.neotechnology.com Cellphone: +46 706 534857 _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
