When pool connection is not heath, the connection.close() sometime will raise an exception.

[cnkailyn]

Backgroud:
I got an issue raised from neo4j:
this this the exception logs:

Then I checked the source code here:

The direct issue is the connection is not health, maybe the TCP have already closed, but we still call connection.close(), then it raise that 'RuntimeError: unable to perform operation on <TCPTransport closed=True reading=False 0x56126bcdf100>; the handler is closed'.

there should add a try for connection.close() or add some conditions like:
if not conncetion.tcp.closed: conncetion.close()

[robsdedude]

Hi and thanks for the bug report. It'd be a great help for me if you could share some extra information with me so that I can understand the problem in more detail:

• What operating system are you using?
• What event loop are you running? I'm suspecting that this is run using uvloop and not asynio.
• Please share the full stack trace of the error (ideally as text, and not a screenshot, but better a screenshot than nothing)
• If you can reproduce the error, I'd be very happy to see driver debug logs so that I can see what the connection in question was doing before the failure. Here are the API docs on how to enable the debug logs: https://neo4j.com/docs/api/python-driver/current/api.html#logging

[robsdedude]

Hello again @cnkailyn 👋

Can you please share the requested information so that I can start investigating?