kombu reconnecting needs better exception catching
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Andrea Rosa |
Bug Description
NOTE(comstud): Amended this bug report to include another case that needs fixing. Will fix together.
(Reported by Andrea:)
If there are some socket issues, e.g. after a restart of the rabbitmq server, the declare consume class can raise an exception when try to declare its queue.
2011-10-31 09:17:19,073 ERROR nova.rpc [-] Exception during message handling
(nova.rpc): TRACE: Traceback (most recent call last):
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: rval = node_func(
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: raise Error(str(e))
(nova.rpc): TRACE: Error: (320, u"CONNECTION_FORCED - broker forced connection closure with reason 'shutdown'", (0, 0), '')
(nova.rpc): TRACE:
(Reported by comstud:)
http://
Changed in nova: | |
assignee: | nobody → Andrea Rosa (andrea-rosa-m) |
importance: | Undecided → Medium |
status: | Incomplete → In Progress |
summary: |
- exception for decalre consumer in the case of socket error + exception for declare consumer in the case of socket error |
summary: |
- exception for declare consumer in the case of socket error + kombu reconnecting needs better exception catching |
description: | updated |
Changed in nova: | |
milestone: | none → essex-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-3 → 2012.1 |
What would be the expected behavior ?