Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 655141

Summary: cluster broker exits with "error deliveryRecord no update message."
Product: Red Hat Enterprise MRG Reporter: Alan Conway <aconway>
Component: qpid-cppAssignee: Alan Conway <aconway>
Status: CLOSED ERRATA QA Contact: ppecka <ppecka>
Severity: high Docs Contact:
Priority: high    
Version: 1.3CC: freznice, iboverma, jneedle, tross
Target Milestone: 1.3.2-RC1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-cpp-mrg-0.7.946106-26 Doc Type: Bug Fix
Doc Text:
When a new broker attempted to join a cluster with clients receiving messages with a time to live (TTL) limit specified, it could fail with the "error deliveryRecord no update" or "error empty update queue" message. This update corrects handling of TTL in a cluster, and new brokers can now join as expected.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-15 12:11:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 654872    
Attachments:
Description Flags
Reproducer test patch none

Description Alan Conway 2010-11-19 17:48:38 UTC 
Description of problem:

A broker joining a cluster has "error deliveryRecord no update message" which leads to shutdown.

Version-Release number of selected component (if applicable):1036871

How reproducible: easy

Steps to Reproduce:

Apply attached patch to cluster_tests.py and do:
  make check TESTS=run_cluster_tests CLUSTER_TESTS="*dr_no_message"
 
Actual results: broker exits with error

Expected results: no error

Additional info:
Comment 1 Alan Conway 2010-11-19 18:24:49 UTC 
Created attachment 461620 [details]
Reproducer test patch
Comment 2 Alan Conway 2010-11-22 16:02:55 UTC 
Another symptom of this bug is the updatee shutting down with: "error empty update queue"
Comment 3 Alan Conway 2010-11-22 16:16:59 UTC 
Fixed in r1037763
Comment 5 Alan Conway 2011-01-26 19:57:36 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: New broker joins a cluster where clients are receiving messages with TTL (time-to-live)

Consequence: The new broker fails to join with "error deliveryRecord no update message" or "error empty
update queue"

Fix: Correct handling of TTL in a cluster.

Result: Brokers join with no error.
Comment 7 ppecka 2011-02-01 10:08:39 UTC 
VERIFIED RHEL 5.6 i386 / x86_64:

packages used
qpid-cpp-mrg-0.7.946106-27.el5.src.rpm
qpid-tools-0.7.946106-12.el5.src.rpm
openais-0.80.6-28.el5

--> VERIFIED
Comment 8 Jaromir Hradilek 2011-02-09 13:13:22 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,8 +1 @@
-Cause: New broker joins a cluster where clients are receiving messages with TTL (time-to-live)
+When a new broker attempted to join a cluster with clients receiving messages with a time to live (TTL) limit specified, it could fail with the "error deliveryRecord no update" or "error empty update queue" message. This update corrects handling of TTL in a cluster, and new brokers can now join as expected.-
-Consequence: The new broker fails to join with "error deliveryRecord no update message" or "error empty
-update queue"
-
-Fix: Correct handling of TTL in a cluster.
-
-Result: Brokers join with no error.
Comment 9 errata-xmlrpc 2011-02-15 12:11:32 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0217.html