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

Crash on COM_CHANGE_USER with disable_sescmd_history=true

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.3.6
    • 2.3.7
    • readwritesplit
    • None

    Description

      The code that discards the session command history will cause a crash if the first session command that is executed is COM_CHANGE_USER and session command history is disabled. Removing disable_sescmd_history=true and adding prune_sescmd_history=true will prevent the crash.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MXS-2451 MaxScale crashes on startup.

          • Major - Major loss of function.
          • Closed

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 3h
                  3h

                  Git Integration

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