Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.5.0
-
None
-
None
-
I found this by setting up a debug point on the handshake. But as I saw it the flush could still happen shortly after causing intermittent issues with SASL clients.
The flush should be deferred until the initial handshake is finished. This is as simple as only doing the flush if the first packet was received, and that would be enough for this.
The solution I'm implementing is to differentiate flushes from scheduled flushes, and doing a regular flush if the first packet was received.
I found this by setting up a debug point on the handshake. But as I saw it the flush could still happen shortly after causing intermittent issues with SASL clients. The flush should be deferred until the initial handshake is finished. This is as simple as only doing the flush if the first packet was received, and that would be enough for this. The solution I'm implementing is to differentiate flushes from scheduled flushes, and doing a regular flush if the first packet was received.
Attachments
Issue Links
- links to