[MXS-4954] Don't send errors if client has already sent a COM_QUIT Created: 2024-01-23 Updated: 2024-02-02 Resolved: 2024-02-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbclient |
| Affects Version/s: | 6.4.13, 22.08.11, 23.02.8, 23.08.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-201 |
| Description |
|
If the client has sent a COM_QUIT and the session is about to close, MaxScale tries to write an error to the client's TCP socket with a message of Connection killed by MaxScale. This is unnecessary and has previously caused some problems in the ODBC test suite. |
| Comments |
| Comment by markus makela [ 2024-02-02 ] |
|
This actually only happens when the client TCP socket receives a hangup event in which case MaxScale writes a Connection killed by MaxScale error to the TCP socket. If it's an actual hangup event, this is a little useless as the client may not receive it at all. For internally generated fake hangup events, it serves a purpose but they are rarely seen. |