| Summary: | Creating a queue with invalid settings results in no queue but only its management object exists | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Pavel Moravec <pmoravec> | |
| Component: | qpid-cpp | Assignee: | Pavel Moravec <pmoravec> | |
| Status: | CLOSED ERRATA | QA Contact: | Petra Svobodová <psvobodo> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 3.0 | CC: | gsim, jross, pmoravec, psvobodo, sauchter | |
| Target Milestone: | 3.1 | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | qpid-cpp-0.30-2 | Doc Type: | Bug Fix | |
| Doc Text: |
It was discovered that an attempt to create a queue with invalid settings created management object for the queue, but not the queue itself. This caused the user to assume a management queue had been created, when in fact the management object contained no attached queue. The error handling mechanism is now updated to ensure the management object is not created if a queue request contains invalid settings.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1168261 (view as bug list) | Environment: | ||
| Last Closed: | 2015-04-14 13:47:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1168261 | |||
Just FYI, the behaviour has been changed since MRG 2.3 / qpid 0.18, where the queue is created (despite the QMF error returned), what prevents successfull broker restart later on. Fixed in upstream by commit r1543449. Now the non existing queue object is not displayed in the "qpid-config queues" list. Verified on qpid-cpp-0.30-3, qpid-tools-0.30-1 on Rhel6.6-i386 and x86_64. --> VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0805.html |
Description of problem: An attempt to create a queue with invalid settings (like max-queue-count < flow-stop-count) returns a QMF error and the queue is not created (can't send messages there or subscribe a consumer to it). But relevant QMF object is still present (listing all queues finds it). Version-Release number of selected component (if applicable): qpid-cpp-server-0.22-23.el6.x86_64 How reproducible: 100% Steps to Reproduce: 0. rm -rf /var/lib/qpidd/* /var/lib/qpidd/.*; service qpidd restart 1. qpid-config add queue WrongQueue1 --max-queue-count=1 --flow-stop-count=100 --durable 2. qpid-send -a WrongQueue1 -m1 3. qpid-config queues WrongQueue1 Actual results: 1. returns: Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text': 'invalid-argument: Queue "WrongQueue1": qpid.flow_stop_count=100 must be less than qpid.max_count=1 (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/broker/QueueFlowLimit.cpp:58)'} 2. returns: 2013-10-30 07:57:18 [Client] warning Exception received from broker: not-found: not-found: Queue not found: WrongQueue1 (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/broker/QueueRegistry.cpp:127) [caused by 2 \x08:\x01] qpid-send: Queue WrongQueue1 does not exist 3. returns: Queue Name Attributes =================================== WrongQueue1 --durable --max-queue-count=1 --flow-stop-count=100 Expected results: 1. and 2. as actual results, but 3. should return no such queue Additional info: Continuing in the reproducer, restarting the broker and running "qpid-config queues WrongQueue1" again shows no such queue exists - despite the queue was attempted to be created as durable. That just supports the theory that Queue object has not been created but its Management version was.