add timer for recieving closeok, force close socket after a while

[kickster97]

No description provided.

[github-actions]

Main benchmark
'Average publish rate: 354126.3 msgs/s'
'Average consume rate: 354235.9 msgs/s'

PR benchmark
'Average publish rate: 354165.3 msgs/s'
'Average consume rate: 352251.6 msgs/s'

Keep in mind, these numbers are not representative of LavinMQ's peak performance.
It is rather an indication of how the changes of this pull request affects the performance of the main branch.

[carlhoerberg]

this only works if the client still sends frames, but imagine a client that just consumes but doesn't properly send the CloseOk frame, eg. because it's busy with other things.. One possibility is to start a new fiber when we close the client, that sleeps 5s, checks if the connection is still open and then force closes it.

[carlhoerberg]

The down side is of course that if we closed 1M connections, and thus spawn 1M new fibers, that can be very memory intensive..

[carlhoerberg]

or we set a read_timeout on the socket when we try to gracefully close the client, so the read_loop will raise an TimeoutError if the client is silent.

[kickster97]

i think my last commit adds it in the way you're thinking, not sure how to test it easily

[spuun]

I guess this if-statement isn't needed now with the read_timeout set? Instead we can check if @running == false, log something about timeout and break the loop? (cleanup and close_socket is always done thanks to the ensure block).