Hi,
I have encounter a similar behavior in the retry mechanism: at org.neo4j.driver.internal.retry.ExponentialBackoffRetryLogic#retryWorkInEventLoop
there is a WARN log with entire stack-trace that seems redundant to the driver's users.
version: 1.7....
