Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to solve Neo4jError: read ECONNRESET

See original GitHub issue

Since we started using this driver we are getting following error frequently.

{ Neo4jError: read ECONNRESET
    at new Neo4jError (D:\home\site\wwwroot\node_modules\neo4j-driver\lib\v1\error.js:76:132)
    at newError (D:\home\site\wwwroot\node_modules\neo4j-driver\lib\v1\error.js:66:10)
    at NodeChannel._handleConnectionError (D:\home\site\wwwroot\node_modules\neo4j-driver\lib\v1\internal\ch-node.js:330:41)
    at emitOne (events.js:121:20)
    at TLSSocket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9) code: 'ServiceUnavailable', name: 'Neo4jError' }

Is there any way to fix this ? We are using connectionPoolSize = 0 while creating driver. Also using nodejs promise way run the neo4j queries and doing session.close() every time.

Issue Analytics

State:
Created 5 years ago
Comments:14 (4 by maintainers)

Top GitHub Comments

1reaction

rjgmail88commented, Jun 27, 2018

We are good on this. Thank you.

0reactions

danielnitschecommented, Nov 4, 2022

Right now there is no built-in way to log retries. We will add it to 1.7 version of the driver. You could insert logging of retries in the function itself:

Sorry to dig up an old thread – is this now possible?

Edit: found it, thanks: https://github.com/neo4j/neo4j-javascript-driver/pull/380