Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-21 Thread Mattias Persson
I think for such a scenario you'd need read locks which gets upgraded to write locks when modifying. Consider this simple scenario w/o read locks: Thread ONE: get relationship R Thread TWO: get relationship R Thread TWO: delete relationship R and commit transaction Thread ONE: do any modification

Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-21 Thread Aseem Kishore
I'm definitely modifying the graph at the same time; that's why this is happening. But my assumption was that that shouldn't be breaking Neo4j -- I thought requests are transactional/serialized. I don't have a repro test at the moment, but the behavior is really simple. Here's an example analogy.

Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-21 Thread Aseem Kishore
On Sun, Nov 20, 2011 at 10:43 PM, Andres Taylor andres.tay...@neotechnology.com wrote: Cypher in 1.4 was very experimental. If you are using Cypher, I would suggest you move to 1.5 ASAP - a lot has happened there. If you still have the same problems with 1.5, then we can start looking for the

Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-21 Thread Aseem Kishore
Mattias, thanks for the suggestion, but to clarify, we're using the server as-is, with the REST API; we're not using the Java API. Is there any way we can specify locking like you suggest via the server config or similar? Aseem On Mon, Nov 21, 2011 at 12:26 AM, Mattias Persson

Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-21 Thread Aseem Kishore
One more point of clarification: these are concurrent REST API requests. One request is deleting a relationship, another request is querying for a(nother) relationship. A simple analogy is a user unliking one thing on Facebook then immediately liking something else. I wouldn't expect the

Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-21 Thread Mattias Persson
2011/11/21 Aseem Kishore aseem.kish...@gmail.com One more point of clarification: these are concurrent REST API requests. One request is deleting a relationship, another request is querying for a(nother) relationship. A simple analogy is a user unliking one thing on Facebook then immediately

[Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-20 Thread Aseem Kishore
Hey guys, If we put our app under a bit of load, creating and removing nodes and relationships concurrently, sometimes we get back a 500 Internal Server Error from the REST API when we do a traverse or Cypher query. Here's an example stack trace: https://gist.github.com/1381423 We're running

Re: [Neo4j] Relationship not found error while traversing/querying (REST API)

2011-11-20 Thread Andres Taylor
On Mon, Nov 21, 2011 at 3:22 AM, Aseem Kishore aseem.kish...@gmail.comwrote: Hey guys, If we put our app under a bit of load, creating and removing nodes and relationships concurrently, sometimes we get back a 500 Internal Server Error from the REST API when we do a traverse or Cypher query.