[MXS-4409] Unexpected result state with MySQL 5.7.36 Created: 2022-11-21 Updated: 2023-04-06 Resolved: 2023-04-06 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 22.08.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Sprint: | MXS-SPRINT-172 |
| Description |
|
A Unexpected result state. cmd: 0x00, len: 7 error is logged after calling a stored procedure that returns at least one resultset. The trailing OK packet appears to be the one that ends up triggering this problem. |
| Comments |
| Comment by Brock Wilson (Inactive) [ 2022-11-22 ] |
|
Attaching customer' maxscale.cnf-2.txt |
| Comment by markus makela [ 2022-11-22 ] |
|
You can get some extra debugging information out from it by adding session_trace=300 under the [maxscale] section. This will produce a detailed log dump for the session when this problem occurs. Although it'll be identical for non-debug builds that you get with log_info enabled. |