Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
I'm sorry to disappoint - we haven't prioritized this as we've mostly gotten away from these errors.
For us, the main source of problems was actually a very slow sht_rm_name_re in our configs. We store connection information in an htable and this regex call was causing the WebSocket module to slow down while iterating over each connection.
We ended up replacing the regex call with explicit sht_rm calls in. our config which solved the problem for us. We do still encounter these WebSocket errors occasionally, and I do believe the pseudocode posted above is still valid.
I'm sorry we haven't take the time to try that out yet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.