[MXS-3392] Reset implementation on failing prepared statement Created: 2021-02-01 Updated: 2021-03-04 Resolved: 2021-02-23 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.5.7 |
| Fix Version/s: | 2.4.17, 2.5.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Diego Dupin | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | CONNECTOR_RELATED | ||
| Sprint: | MXS-SPRINT-125 |
| Description |
|
There seems to be a strange behavior with maxscale when resetting a connection, after having a failed prepared statement.
error is "Unknown prepared statement handler (4294967295) given to MaxScale (1243) " 4294967295 correspond to -1 => this is usually use by COM_STMT_EXECUTE to indicate to execute last prepared statement. mariadb_stmt_execute_direct might send a COM_STMT_CLOSE + COM_STMT_EXECUTE with id -1. I don't understand what can cause this, because error occur on reset, but there is a strange behaviour with maxscale with this special "-1" feature. |
| Comments |
| Comment by markus makela [ 2021-02-01 ] |
|
What version of MaxScale is this? |
| Comment by Diego Dupin [ 2021-02-01 ] |
|
this is version 2.5.3 |
| Comment by markus makela [ 2021-02-01 ] |
|
Can you retest with the latest 2.5.7 release? |
| Comment by Diego Dupin [ 2021-02-01 ] |
|
tested with 2.5.7 with exactly the same result |