neography
neography copied to clipboard
No error message or stack trace provided on Neography::NeographyError message
I'm getting the following error when trying to run a create_unique_node through neography. Here's an sample from the log with neography logging set to true:
E, [2014-11-17T12:09:06.570972 #20444] ERROR -- : {:body=>"", :headers=>{"Content-Length"=>"113", "Content-Type"=>"application/json; charset=UTF-8", "Access-Control-Allow-Origin"=>"*", "Server"=>"Jetty(6.1.25)"}, :status=>500, :reason_phrase=>"Internal Server Error", :remote_ip=>"127.0.0.1", :local_port=>49735, :local_address=>"127.0.0.1"} error: {
"exception" : "NullPointerException",
"fullname" : "java.lang.NullPointerException",
"stacktrace" : [ ]
}
Here's the backtrace from the point in my code where it transitions to neography:
neography-1.6.0/lib/neography/connection.rb:245→ raise_errors
neography-1.6.0/lib/neography/connection.rb:217→ handle_4xx_500_response
neography-1.6.0/lib/neography/connection.rb:188→ return_result
neography-1.6.0/lib/neography/connection.rb:159→ evaluate_response
neography-1.6.0/lib/neography/connection.rb:71→ block (3 levels) in <class:Connection>
neography-1.6.0/lib/neography/connection.rb:79→ log
neography-1.6.0/lib/neography/connection.rb:62→ block (2 levels) in <class:Connection>
neography-1.6.0/lib/neography/rest/node_indexes.rb:106→ create_unique_node
/home/user/prod/radar-jobs/releases/28/jobs/neo4j_job.rb:104→ create_node
Looking for suggestions on how to best debug/fix this.
Relevant information: neography gem 1.6.0 ruby 2.1.4p265 (2014-10-27 revision 48166) [x86_64-linux] neo4j 1.9.9
Did we ever figure this one out? It worked on some of the machines, but not others... some kind of weird file issue if I recall...
It's still happening after I run many batch jobs. Eventually gets to the point where every attempt to create a node kicks off this error. Have to restart the service to get neo4j to start accepting new inserts again