[MXS-4639] COM_STMT_PREPARE halts the processing pipeline Created: 2023-06-13  Updated: 2023-09-27

Status: Open
Project: MariaDB MaxScale
Component/s: Protocol
Affects Version/s: 6.4.7
Fix Version/s: None

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


 Description   

The JDBC connector can send a COM_STMT_PREPARE command followed immediately by a COM_STMT_EXECUTE command. Currently MaxScale halts the processing of incoming packets while the COM_STMT_PREPARE is being executed (it's a session command) and only continues with the COM_STMT_EXECUTE once it's done.

There's no need to do that as all of the information needed to route is known at the time the COM_STMT_PREPARE is read. A COM_STMT_EXECUTE should be an exception and should be routed even if a session command is being executed.


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