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

Bug 1048197

Summary: Make queue sequence ID persistent
Product: Red Hat Enterprise MRG Reporter: Pavel Moravec <pmoravec>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED UPSTREAM QA Contact: Messaging QE <messaging-qe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jross, pmoravec
Target Milestone: ---Keywords: Improvement, TestCaseProvided
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:34:45 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 785156    

Description Pavel Moravec 2014-01-03 11:17:50 UTC
Description of problem:
Implementing RFE in https://bugzilla.redhat.com/show_bug.cgi?id=691411, the sequence numbers introduced there do not survive broker restart. That substantially limits usage of the RFE.

Please ensure the sequence numbers persist broker restart.


Version-Release number of selected component (if applicable):
MRG 3.0 (qpid-cpp 0.22-29)


How reproducible:
100%


Steps to Reproduce:
qpid-send -a "ring; {create:sender, node: {durable:true, x-declare: {arguments: {'qpid.queue_msg_sequence':'mySeq', 'qpid.policy_type':'ring', 'qpid.max_count':4}}}}" -m 7 --durable=yes
qpid-receive -a "ring; {mode:browse}" -m 10 --print-headers=yes --print-content=no > first.txt
service qpidd restart
qpid-receive -a "ring; {mode:browse}" -m 10 --print-headers=yes --print-content=no > second.txt
diff first.txt second.txt



Actual results:
2c2
< Properties: {mySeq:4, sn:4, ts:1388743508257534084, x-amqp-0-10.routing-key:ring}
---
> Properties: {mySeq:1, sn:4, ts:1388743508257534084, x-amqp-0-10.routing-key:ring}
5c5
< Properties: {mySeq:5, sn:5, ts:1388743508257544604, x-amqp-0-10.routing-key:ring}
---
> Properties: {mySeq:2, sn:5, ts:1388743508257544604, x-amqp-0-10.routing-key:ring}
8c8
< Properties: {mySeq:6, sn:6, ts:1388743508257551938, x-amqp-0-10.routing-key:ring}
---
> Properties: {mySeq:3, sn:6, ts:1388743508257551938, x-amqp-0-10.routing-key:ring}
11c11
< Properties: {mySeq:7, sn:7, ts:1388743508257559208, x-amqp-0-10.routing-key:ring}
---
> Properties: {mySeq:4, sn:7, ts:1388743508257559208, x-amqp-0-10.routing-key:ring}


Expected results:
files are the same


Additional info:

Comment 1 Pavel Moravec 2014-05-26 12:54:57 UTC
It is not simple to store on the disk the actual value of queue sequence ID. See the difficulties of similar request for exchange sequeuence ID in https://reviews.apache.org/r/19566/ .

Comment 6 Red Hat Bugzilla 2025-02-10 03:34:45 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.