Neo4j, graphaware: After catching an exception, another query will not execute.

Question

I am connecting to neo4j the normal way and i can run queries no problem.
During testing, i wrote a query that should fail (due to uniqueness constraint), the query does fail as expected and i catch the exception.
The problem is when i try to execute the next query in the queue, it just hangs (longer than timeout).
I don't suppose that is normal behavior.

 try{
     $result = $neo->run ($query);
 }
 catch (Exception $e) {
          // handle it
 }

 // all good so far
 // now we attempt:

try{
    $result = $neo->run ($next_query);
 }
 catch (Exception $e) {
          // handle it
 }
// hangs longer than timeout

if i remove the failed query from the queue, everything completes

Answered on the github issue https://github.com/graphaware/neo4j-php-client/issues/86#issuecomment-278420273 — Christophe Willemsen, Feb 08 '17 at 21:36

score 0 · Answer 1 · answered Feb 08 '17 at 00:19

So it seems that the exception thrown by the php-client breaks the connection to neo4j.
If i modify the code to the following, it all works fine.

try{
     $result = $neo->run ($query);
 }
 catch (Exception $e) {
          // handle it
      connect_to_neo()
 }

 // all good so far

try{
    $result = $neo->run ($next_query);
 }
 catch (Exception $e) {
          // handle it
 }
 // all good, $next_query gets executed

I do not think that an exception that breaks the connection is desired behavior. Will raise the issue on github.

Neo4j, graphaware: After catching an exception, another query will not execute.

1 Answers1