beast: What is the websocket's state if async_close fails?
Beast Version 1.70 OpenSSL version 1.1.1a
We use Websocket over SSL. A great number of times when calling async_close, the operation fails with error code 1 and message “stream truncated”.
We are wondering what the state of the websocket is after the async_close has failed.
is it open, closed or undefined?
We found that in some instances a pending async_read operation was not cancelled after the async_close was run and failed. In some other instances the async_read operation was indeed cancelled.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (6 by maintainers)
Thank you so much for your help!
To be honest we are not sure if async_close completed with an error, or it never completed after 10 minutes. Our logs are mixed in the same file. We have improved our logging and will post an update if we have more data.