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

debug assert at backend.cc:104 failed: !is_waiting_result()

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Cannot Reproduce
    • 2.3.9
    • 2.5.0
    • schemarouter
    • None

    Description

      The following assertion happens when both the abstracted services are stopped and a command line connection is opened and then interrupted with a SIGINT.

      2019-07-19 08:46:03   info   : Servers and connection counts:
      2019-07-19 08:46:03   info   : MaxScale connections : 0 (0) in  127.0.0.1:4006 RUNNING (only)
      2019-07-19 08:46:03   info   : MaxScale connections : 0 (0) in  127.0.0.1:4009 RUNNING (only)
      2019-07-19 08:46:03   info   : Connected RUNNING (only) in      127.0.0.1:4006
      2019-07-19 08:46:03   info   : Connected RUNNING (only) in      127.0.0.1:4009
      2019-07-19 08:46:03   info   : Started SchemaRouter-Router client session [23] for 'maxuser' from ::ffff:127.0.0.1
      2019-07-19 08:46:03   info   : (23) > Command: COM_QUERY, stmt: select @@version_comment limit 1 
      2019-07-19 08:46:03   info   : (23) Route query to      s1 [127.0.0.1]:4006 <
      2019-07-19 08:46:10   info   : (23) > Command: COM_QUIT, stmt:  
      2019-07-19 08:46:10   info   : (23) Session write, routing to all servers.
      2019-07-19 08:46:10   info   : (23) Route query to slave        127.0.0.1:4006
      2019-07-19 08:46:10   error  : (23) debug assert at backend.cc:104 failed: !is_waiting_result()
      

      Attachments

        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:

              Git Integration

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