rpc server won't stop if could not connect to amqp server

Bug #1706839 reported by Shaw Ho
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

We start an multi-process rpc server using RPCServer,and connect to a AMQP server such as rabbitmq. If the AMQP server is down when starting rpc server, the log will print AMQP server reconnecting information, now stop the rpc server, only the parent process exit, the child processes are still alive, and the logs still printing.

I debugged the program, and found that the program block at the 'stop' method of MessageHandlingServer. The reason is that the call to 'start' method in MessageHandlingServer won't finish if AMQP server can't be connected, and the 'stop' must run after 'start' have been executed due to the 'ordered' decorator.

My opinion is that the stop action of rpc server should not rely on the AMQP server's status.

Shaw Ho (hexiaoxi)
description: updated
description: updated
Ken Giusti (kgiusti)
Changed in oslo.messaging:
status: New → Confirmed
importance: Undecided → Medium
norman shen (jshen28)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.