Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.4.17, 2.5.11
-
Component/s: Protocol
-
Labels:None
Description
The capability is supported by MaxScale but is not advertised. This causes connectors that could use it (Connector/J) to use less optimal SQL to retrieve information about the session state.
Attachments
Issue Links
- causes
-
MXS-3704 MaxScale always advertises the SESSION_TRACK capability even with servers that don't support it (XPand)
-
- Closed
-