[MXS-4650] Unknown prepared statement handler error with readconnroute Created: 2023-06-20  Updated: 2023-10-25  Resolved: 2023-08-21

Status: Closed
Project: MariaDB MaxScale
Component/s: readconnroute
Affects Version/s: 6.4.7
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Incomplete Votes: 0
Labels: None

Sprint: MXS-SPRINT-186, MXS-SPRINT-187, MXS-SPRINT-188

 Description   

These get logged for some reason in MaxScale.

Unknown prepared statement handler (0) given to MaxScale for COM_STMT_CLOSE

This appears to be a case where a COM_STMT_CLOSE is sent without a COM_STMT_PREPARE being sent. Another case was also seen where two COM_STMT_CLOSE were sent in a row.



 Comments   
Comment by markus makela [ 2023-07-18 ]

The 6.4.8 version will contain a warning about partially received COM_STMT_CLOSE packets which should rule that out as a cause. If these end up being logged, it means there's a bug somewhere in MaxScale that splits a packet in half.

There is also additional info level messages that log the connection attributes of each client. This should help identify which driver is being used to connect to MaxScale which in turn helps out rule problems like CONC-522.

Generated at Thu Feb 08 04:30:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.