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

Failed to read message exception #954

Open
ErangaD opened this issue Dec 10, 2022 · 2 comments
Open

Failed to read message exception #954

ErangaD opened this issue Dec 10, 2022 · 2 comments

Comments

@ErangaD
Copy link

ErangaD commented Dec 10, 2022

I use the latest py2neo version and in the server logs I can see this error message keeps appearing (not always). It affects the users of the application sometimes.
Failed to read message

I tried to debug the issue. I am using bolt connection inside an azure app service. This happens when the graph.run(query).data() is executed and after few minutes (usually 3 - 4 minutes) this throws the 'Failed to read message' exception. It seems this is thrown inside the Wire read.
Screenshot 2022-12-10 at 14 30 18
I have seen a similar issue reported here #844
Any solution or workaround is highly appreciated.

@ErangaD
Copy link
Author

ErangaD commented Dec 12, 2022

I also see this in Neo4j server debug logs.

Screenshot 2022-12-12 at 09 40 29

@ErangaD
Copy link
Author

ErangaD commented Dec 17, 2022

As a workaround, I was able to resolve this issue by executing a dummy query once a minute. It is not the best solution but it works. I think what happens is the database connection gets abandoned after some time if the connection is not used for a while. And that connection is used even though it is closed which leads to this error. I guess if this library can address this issue, it would be great.

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