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

Session Expired on Query #180

Open
alex-laycalvert opened this issue Sep 18, 2023 · 2 comments
Open

Session Expired on Query #180

alex-laycalvert opened this issue Sep 18, 2023 · 2 comments

Comments

@alex-laycalvert
Copy link
Contributor

I'm running some queries using the cypher queries and just passing text and parameters and on some instances, the queries error out with a code of Session Expired and a message saying Neo4j Error: No longer possible to write to server at <server>. The actual text length varies and it seems like they are erroring out before even attempting to run.

About my setup, I have a separate singleton class I'm using as a wrapper around Neode which when instantiated for the first time just sets the neode instance to new Neode(...). I don't know if this is screwing up some of the session creation or any pooling that happens.

Is this common on larger queries or is there a connection setting that is going wrong somewhere?

Thanks.

@alex-laycalvert
Copy link
Contributor Author

Looks like every time cypher readCypher or writeCypher is called, a new session is made so I don't think there's some global session that's expiring, but maybe I am messing it up with how I have my project configured.

@alex-laycalvert
Copy link
Contributor Author

Looks like this is related to this article. I seem to only be having this issue in production.

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

1 participant