In preparation for operation timeout events.
When the pdu processing limit is hit, we still attempt to read another
PDU. If we succeed, the ber_get_next call in the read callback will
abort since a full PDU is already present.
Stats now logs all operations, stats2 additionally intermediate messages
We reset the connection pointer on a destruction attempt, avoid the
Do not log when receiving the last bytes on a connection. Log failed
This alone doesn't make the server do a round robin.
There was still a race where the connection could be freed as the
operation was still being used.
The connection might be ready to read (close) but if we can't destroy it
yet, we don't want the callback to trigger all the time or process new