MXS-2562: Always send errors with sequence number 1

As is explained in MDEV-19893:

   Client reads from socket, gets the packet from 1. with seqno=0, which
   it does not expect, since seqno is supposed to be incremented. Client
   complains, throws tantrums and exceptions.

To cater for clients that do not expect out-of-bound messages
(i.e. server-initiated packets with seqno 0), all messages generated by
MaxScale should use at least sequence number 1.
This commit is contained in:
Markus Mäkelä 2019-06-27 18:32:27 +03:00
parent 5ab5e914e7
commit 74d15cee09
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19

View File

@ -1594,7 +1594,7 @@ static int gw_client_hangup_event(DCB* dcb)
errmsg += ": " + extra;
}
modutil_send_mysql_err_packet(dcb, 0, 0, 1927, "08S01", errmsg.c_str());
modutil_send_mysql_err_packet(dcb, 1, 0, 1927, "08S01", errmsg.c_str());
}
dcb_close(dcb);
}