| Subject: | Unhandled exception for Can't connect... |
Been tracking this bug down for a few days.
I think the streaming REST would help alleviate this problem. It is occurring after multiple
queries, so perhaps the old client has not fully disconnected or something? Mostly CYPHER
queries so I can't bulk them(and very disparate). Would be nice to have a try_again or reconnect
feature that would wait a few seconds. This is part of batch processing for many genes so there
is really no hurry or worry for speed reasons.
It happens about 35 - 40 minutes into the program which runs all cypher queries and several
per data pont. Smaller datasets finish no problem. The server is still up and running, I know
this from a batch insert process that is inserting millions of relationships and it is still running
unabated for 5 days with no problem / interruption.
Let me know if I can provide any more useful data.
Use of uninitialized value $e in die at
/opt/local/lib/perl5/site_perl/5.16.1/REST/Neo4p/Query.pm line 61.
Job 'JobHandlerWorker::context_query' died: malformed JSON string, neither array, object,
number, string or atom, at character offset 0 (before "Can't connect to 127...") at
/opt/local/lib/perl5/site_perl/5.16.1/REST/Neo4p/Agent.pm line 231.
...propagated at /opt/local/lib/perl5/site_perl/5.16.1/REST/Neo4p/Query.pm line 61.