-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.5.4, 2.5.5
-
Fix Version/s: 2.5.6
-
Component/s: Core, readconnroute
-
Labels:None
-
Sprint:MXS-SPRINT-119, MXS-SPRINT-120
While, testing a newer maxscale version 2.5.4 for some potential bottlenecking and have an error popping into the maxscale log. Users connecting and processing correctly.
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x05, len: 1 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x03, len: 42 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x03, len: 40 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x03, len: 33 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x03, len: 32 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x03, len: 48 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0xfe, len: 5 server: tdb1m2
|
2020-10-20 20:36:03 error : (1672) Unexpected result state. cmd: 0x0a, len: 67 server: tdb1m2
|