[MXS-4456] Modules may end up calling clientReply directly in routeQuery Created: 2022-12-16  Updated: 2023-03-06  Resolved: 2023-03-06

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 23.08.0

Type: Task Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-178

 Description   

The way the routing currently works is that the client protocol's expected response count is incremented before the call to routeQuery is done. This avoids the problem where the response count goes negative if a call to clientReply is done inside the routeQuery call.

Modify the modules that do this to instead return it after the function has finished. Mechanisms for this are already available.


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