Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neography should handle clients that have closed explicitly, or not use persistent connections #193

Closed
sebbacon opened this issue Sep 10, 2014 · 3 comments

Comments

@sebbacon
Copy link

The embedded Jetty in neo4j has an idle connection timeout of 30 seconds.

The default configuration parameter for neography that is passed to Excon is to use persistent connections. Excon expects to be able to write to a persistent socket, but this is not always the case.

Neography should either default to passing :persistent => false to the Excon connection constructor, or it should catch IO exceptions relating to closed connections (broken pipe when writing, EOF when reading) and create a new connection if necessary.

@klobuczek
Copy link
Contributor

+1

1 similar comment
@seenickcode
Copy link

+1

@delmendo
Copy link

They should close this. The configure block lets you set persistent to false

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants