Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: Icebox
-
Component/s: N/A
-
Labels:
-
Epic Link:
-
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.