Bug 1041512 - [amqp1.0] message timestamps are not working for amqp1.0 messages
Summary: [amqp1.0] message timestamps are not working for amqp1.0 messages
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 16:43 UTC by Petr Matousek
Modified: 2020-11-04 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-5285 0 None None None Never

Description Petr Matousek 2013-12-12 16:43:53 UTC
Description of problem:

Messages sent by amqp1.0 client are not timestamped on the broker. 

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

How reproducible:
100%

Steps to Reproduce:
1. qpidd --enable-timestamp yes
2. spout --connection-options "{protocol: 'amqp1.0'}" "q;{create:always}"
3. drain q
4. no timestamp on received message

Actual results:
No timestamps on received messages

Expected results:
timestamps present on received messages if timestamping enabled

Additional info:

# qpidd --enable-timestamp yes
# $cppapi/spout "q;{create:always}"
# $cppapi/drain q
Message(properties={spout-id:ae7fd52c-165a-4af5-8c49-e620629ca6c0:0, x-amqp-0-10.routing-key:q, x-amqp-0-10.timestamp:1386865261}, content='<void>')
# $cppapi/spout --connection-options "{protocol: 'amqp1.0'}" q
# $cppapi/drain q
Message(properties={spout-id:f3032b1d-6a69-4ba0-9827-89829438fb3e:0}, content='<void>')

Comment 1 Gordon Sim 2013-12-12 16:54:03 UTC
The timestamp field is 0-10 specific. Something similar could of course be offered by adding a custom annotation for it, but this would be qpidd specific behaviour.


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