[MXS-1987] Add option to suppress "Connection killed by MaxScale" messages Created: 2018-07-23  Updated: 2022-06-05  Resolved: 2020-01-17

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: None
Fix Version/s: Icebox

Type: New Feature Priority: Major
Reporter: Valerii Kravchuk Assignee: Niclas Antti
Resolution: Won't Fix Votes: 0
Labels: warning

Epic Link: Router Improvements
Sprint: MXS-SPRINT-96, MXS-SPRINT-97

 Description   

MaxScale produces warnings for clients when backend connections are abruptly closed (abruptly in the sense that the client doesn't initiate the process). For Java connections they look as follows:

...
2018-06-11 15:50:14,953 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Timer-8) IJ030027: Destroying connection that is not valid, due to the following exception: org.mariadb.jdbc.MariaDbConnection@6529b7ed: java.sql.SQLNonTransientConnectionException: (conn:848) Connection killed by MaxScale
...
Caused by: java.sql.SQLException: Connection killed by MaxScale
Query is: SELECT 1
...

These warnings may be considered as exceptions and require restarts.

So, I'd like to request some option for MaxScale to NOT produce these warnings.


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