Bug 1040522 - qpid.sequence_counter is ignored
Summary: qpid.sequence_counter is ignored
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-11 15:00 UTC by Zdenek Kraus
Modified: 2020-11-04 22:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1040526 0 low NEW qpid.sequence_counter argument set to 0 after restart 2021-02-22 00:41:40 UTC

Internal Links: 1040526

Description Zdenek Kraus 2013-12-11 15:00:42 UTC
Description of problem:
Exchange argument 'qpid.sequence_counter' is ignored

// Documentation CITE:
qpid.msg_sequence (bool)
If set to “true”, the exchange inserts a sequence number named “qpid.msg_sequence” into the message headers of each message. The type of this sequence number is int64. The sequence number for the first message routed from the exchange is 1, it is incremented sequentially for each subsequent message. The sequence number is reset to 1 when the qpid broker is restarted.
qpid.sequence_counter (int64)
Start qpid.msg_sequence counting at the given number.
// END CITE

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-29
qpid-cpp-*-0.18-18

How reproducible:
100%

Steps to Reproduce:
1. create exchange with 'qpid.msg_sequence:True' & 'qpid.sequence_counter:10
and listen for messages
./qc2_drain -f "xx;{create:always, node:{type:topic, x-declare:{arguments:{'qpid.msg_sequence':True, 'qpid.sequence_counter':10}}, durable:true}}"

2. check the QMF
./qmf2_list_objects --query-data exchange/xx | ipython
  ## see additional info for results

4. ./qc2_spout "xx"

Actual results:
{'redelivered': False, 'reply-to': None, 'subject': None, 'content_type': None, 'id': None, 'user_id': None, 'correlation_id': None, 'priority': None, 'durable': False, 'ttl': 0, 'properties': {

  'qpid.msg_sequence': 1, 

'spout-id': 'bdc6ce42-6129-4aa0-b2a4-2715c6a5f7de:0', 'x-amqp-0-10.routing-key': None}, 'content': None}

Expected results:
{'redelivered': False, 'reply-to': None, 'subject': None, 'content_type': None, 'id': None, 'user_id': None, 'correlation_id': None, 'priority': None, 'durable': False, 'ttl': 0, 'properties': {

  'qpid.msg_sequence': 10, 

'spout-id': 'bdc6ce42-6129-4aa0-b2a4-2715c6a5f7de:0', 'x-amqp-0-10.routing-key': None}, 'content': None}

Additional info:

QMF listing of xx exchange, see the arguments are correctly set

{'_create_ts': 1386773891936297051,
 '_delete_ts': 0,
 '_object_id': {'_object_name': 'org.apache.qpid.broker:exchange:xx'},
 '_schema_id': {'_class_name': 'exchange',
                '_hash': 'c9bb43df-44ac-63d5-cc1c-6a032025c97d',
                '_package_name': 'org.apache.qpid.broker',
                '_type': '_data'},
 '_update_ts': 1386773894113967633,
 'arguments': {'qpid.msg_sequence': True, 'qpid.sequence_counter': 10},
 'autoDelete': False,
 'bindingCount': 1,
 'bindingCountHigh': 1,
 'bindingCountLow': 1,
 'byteDrops': 0,
 'byteReceives': 0,
 'byteRoutes': 0,
 'durable': True,
 'msgDrops': 0,
 'msgReceives': 0,
 'msgRoutes': 0,
 'name': 'xx',
 'producerCount': 0,
 'producerCountHigh': 0,
 'producerCountLow': 0,
 'type': 'topic',
 'vhostRef': {'_object_name': 'org.apache.qpid.broker:vhost:org.apache.qpid.broker:broker:amqp-broker,/'}}


Note You need to log in before you can comment on or make changes to this bug.