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

Debug assertion in mariadb_backend.cc

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.0
    • Fix Version/s: 6.2.1
    • Component/s: Protocol
    • Labels:
      None

      Description

      If a connection has more than one queued up session command response that needs checking and the first one returns an answer that differs from the accepted one, the connection is closed but the response checking does not stop. This causes a debug assertion in MariaDBBackendConnection::track_query to be hit that can be called by MariaDBBackendConnection::track_response. The correct thing to do is to break out of the loop whenever a partial response or an error is received.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.