[MXS-4139] connection_keepalive sends pings even if client is idle Created: 2022-05-19  Updated: 2023-08-31  Resolved: 2022-06-03

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.20
Fix Version/s: 2.5.21, 6.4.0

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

Issue Links:
Problem/Incident
causes MXS-4440 Lost connection to backend server: ne... Closed

 Description   

With the default configuration of connection_timeout=0s and connection_keepalive=300s, a client that connects to MaxScale and then goes idle is never timed out. This happens because connection_keepalive sends the keepalive pings regardless of the client state. This was not the intended purpose of the feature and it should only send the keepalive pings if the client connection has been idle for less than the configured connection_keepalive value. If the connection goes idle for longer than that, the keepalive pings should stop.


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