-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better error handling when processing messages #178
Comments
Things have changed a little since this issue was originally filed, but it still remains. Here's the updated backtrace:
Here's the command to reproduce the issue: $ amqp-publish --routing-key="topo" --body="$(cat ../datamodel/src/sdx_datamodel/data/topologies/amlight.json)" Basically, this method crashes, on line 59: sdx-controller/sdx_controller/messaging/rpc_queue_consumer.py Lines 46 to 65 in 1dea2a6
I think pika is unhappy about exchange name being an empty string. I'm not sure what this code does though. We should document the purpose of the offending Since the message queue consumer thread crashes, SDX Controller will have to be restarted. But since the message persists in the queue, we will keep crashing and stay unusable until the message queue process is restarted. |
Using amqp-publish, we can publish a message to sdx-controller this way:
However that causes a crash, and then further messages are not handled:
This is less robust than it should be.
The text was updated successfully, but these errors were encountered: