connections are closed uncleanly even when using disconnect()

[kortemik]

Describe the bug
disconnect does not use verifyTransaction therefore connections may be closed uncleanly even when using disconnect()

Expected behavior
disconnect() would use verifyTransaction and close socket only after it has received a reply from server that server is ready to close.

How to reproduce
run

mvn test -Dtest=ManagedConnectionTest#testPooledReboundConnections

multiple times, open and cleanClose counters will mismatch and cause a test to be flaky on L280.

Screenshots

Software version
4.1.0

Desktop (please complete the following information if relevant):

• OS:
• Browser:
• Version:

Additional context
suspected root cause:

this may be affected too by the server's hint message of 0 serverclose 0 which the server tries to send after close transaction is processed and client closes the connection and the counters are based on server's cleanClose.

• sometimes openCount is larger than cleanCloseCount because clean close did not happen
• sometimes cleanCloseCount is larger than openCount because ?

[kortemik]

moving counters in RelpEventOpenCounting and RelpEventCloseCounting from after the accept(frameContext); to before it makes test pass cleanly.

[kortemik]

moving counters in RelpEventOpenCounting and RelpEventCloseCounting from after the accept(frameContext); to before it makes test pass cleanly.

this indicates that there happens an exception while processing these payloads on the server side and following is seen:

[Thread-1] WARN com.teragrep.net_01.eventloop.EventLoop - Detected unexpectedly closed channel