Bug 1024944 - Durable message timestamp is not preserved after broker restart.
Durable message timestamp is not preserved after broker restart.
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: 3.0
: ---
Assigned To: Gordon Sim
Eric Sammons
: Regression
Depends On:
  Show dependency treegraph
Reported: 2013-10-30 11:45 EDT by Leonid Zhaldybin
Modified: 2015-01-21 07:55 EST (History)
4 users (show)

See Also:
Fixed In Version: qpid-cpp-0.22-25.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-01-21 07:55:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Apache JIRA QPID-5284 None None None Never

  None (edit)
Description Leonid Zhaldybin 2013-10-30 11:45:05 EDT
Description of problem:
In the latest Vienna build, the timestamp feature is functional: the broker is capable of adding a timestamp to a message upon its arrival, if '--enable-timestamp yes' option was provided to the broker. However, if the message and the queue to which it was sent are durable, the timestamp added by the broker is supposed to be preserved after broker's restart (that's how it works in MRG/M 2.3 versions). Vienna version of the broker discards the timestamps of the durable messages in the store:

[root@lzhaldyb-rhel64x ~]# qpid-config add queue test --durable
[root@lzhaldyb-rhel64x ~]# qpid-send -a test --durable yes
[root@lzhaldyb-rhel64x ~]# qpid-receive  -a "test;{mode:browse}" --print-content yes --print-headers yes
Durable: true
Properties: {sn:1, ts:1383147149262987329, x-amqp-0-10.routing-key:test, x-amqp-0-10.timestamp:1383147149}

[root@lzhaldyb-rhel64x ~]# service qpidd restart
Stopping Qpid AMQP daemon:                                 [  OK  ]
Starting Qpid AMQP daemon:                                 [  OK  ]
[root@lzhaldyb-rhel64x ~]# qpid-receive  -a "test;{mode:browse}" --print-content yes --print-headers yes
Durable: true
Properties: {sn:1, ts:1383147149262987329, x-amqp-0-10.routing-key:test}

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

How reproducible:

Steps to Reproduce:
1. Start up a broker with "--enable-timestamp yes" option.
2. Send a durable message to the broker.
3. Restart the broker and read the message.

Actual results:
The message does not contain a timestamp after broker restart.

Expected results:
The message timestamp is preserved during broker restart.

Additional info:
Comment 1 Gordon Sim 2013-11-01 06:57:19 EDT
Fixed upstream: https://svn.apache.org/r1537889

Setting skip-errata since this will not have affected a previous MRG release.

(Note that the timestamp uses a field defined only in 0-10 at present and thus is not available from 1.0. See https://issues.apache.org/jira/browse/QPID-5285).
Comment 3 Leonid Zhaldybin 2014-08-06 04:10:37 EDT
Tested on RHEL6 (both i386 and x86_64). This issue has been fixed.

Packages used for testing:



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