[QPID-4247] Qpid-route's error behaviour upon routing a non-existing queue

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 0.14
• Component/s: C++ Broker
• Labels: acl broker error route
• Assignee: Unassigned
• Reporter: Holger Caesar
• Created: 24/Aug/12 14:56
• Updated: 14/Mar/18 20:26
• Resolved: 14/Mar/18 20:26

Description

Hi,
it's me again. I have even another bug, but I didn't want to mention both in one JIRA. I want to route messages from queue Q on broker A to queue Q on broker B (if necessary, I could give it a different name on broker B). The user has full rights to everything.

My first question is, why does the qpid-route tool ask me to specify a source queue and a destination exchange? Aren't queues always bound to the exchange 'amq.direct'? Why don't we just specify two queues?

However, I did try that and when I call
"qpid-route queue add user/pass@localhost:7002 user/pass@localhost:7001 amq.direct Q"
.. I get the following exception for an infinite time period about once per second
"“AMQP-EVAL: 2012-08-24 09:31:55 error Execution exception: not-found: Queue not found: Q“"
Okay, that is my fault, since I did not create Q in advance. But I think the infinite errors are unacceptable. Furthermore, when I crash qpid-route and restart it, I tried the same again and I get:
"Failed: Exception - Duplicate Route - ignoring: amq.direct(Q)"
So apparently it did change something, even though it shouldn't. Trying to clean up the mess via:
"qpid-route queue del user/pass@localhost:7002 user/pass@localhost:7001 amq.direct Q"
just results in "Failed: SystemExit - 0".

I think someone should rework the error handling of that tool. What do you think?

Regards,
Holger