Unexpected internal state when a comment follows a SET statement

When a SQL statement contains a SET command followed by a comment that is separated by a semicolon, the server will respond with two packets. This confuses MaxScale as it expects only one response to the SET command. Version 2.5 and newer are not affected.

This command reproduces the problem:

mysql --delimiter '//' -c -u maxuser -pmaxpwd -h 127.0.0.1 -P 3000 -e "SET net_write_timeout=30; /* hello world */"