[MXS-386] max_sescmd_history should not close connections Created: 2015-09-28  Updated: 2015-09-29  Resolved: 2015-09-29

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 1.2.1
Fix Version/s: 1.3.0

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


 Description   

The way the max_sescmd_history parameter causes readwritesplit to act when the limit is reached is not proper. It should not close the connection but instead it should disable the session command history when the limit is reached.


Generated at Thu Feb 08 03:58:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.