You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Looks like every time cypherreadCypher 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.
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 ofSession Expired
and a message sayingNeo4j 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 tonew 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.
The text was updated successfully, but these errors were encountered: