[MXS-2608] debug assert at backend.cc:104 failed: !is_waiting_result() Created: 2019-07-19  Updated: 2019-10-16  Resolved: 2019-10-16

Status: Closed
Project: MariaDB MaxScale
Component/s: schemarouter
Affects Version/s: 2.3.9
Fix Version/s: 2.5.0

Type: Bug Priority: Minor
Reporter: markus makela Assignee: markus makela
Resolution: Cannot Reproduce Votes: 0
Labels: None

Attachments: File maxscale.cnf    

 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()



 Comments   
Comment by markus makela [ 2019-10-16 ]

No longer reproducible.

Generated at Thu Feb 08 04:15:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.