Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3666

Unexpected internal state when a comment follows a SET statement

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.17
    • Fix Version/s: 2.5.0
    • Component/s: Core
    • Labels:
      None

      Description

      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 */"
      

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.