Closed danielmconrad closed 1 year ago
Thank you for the report. We know that broken connections are not removed from the pool properly. That's why the following specs are reusing the broken connection. We are working on fixing that. It would be great if you could create a failing spec for the initial error that breaks the connection.
We've pulled in the latest 4.4.0 version and no longer have this issue!
Under a normal amount of load, we've begun to see the below error surface. Once we see this error, all subsequent requests will fail, including our health check, which is as simple as
ActiveGraph::Base.read_transaction { |tx| tx.run('MATCH (n) RETURN n LIMIT 1') }
.Database: Neo4j 3.5, 4.4
Gems:
Error: