Red Hat Bugzilla – Bug 504650
If expiration is set on a message published with a ttl, don't reset it
Last modified: 2009-06-12 13:39:44 EDT
Description of problem:
The JMS client calculates the expiration of a message itself on sending the message. The broker should not overwrite the clients value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. send message with both ttl and expiration set
2. subscrbe and receive message
3. check that expiration on received message is exactly the value that was sent
The broker recalculates the expiration.
The expiration should be identical to the value set on sent message.
Created attachment 346899 [details]
Fails before fix with "Expiration did not match".
Created attachment 346901 [details]
Fixed on trunk as r782712.
Fyi: arg::durable=true in test program was supposed to be arg::autoDelete=true. Doesn't affect the core purpose of the test, but as it is it leaves queues lying around.
Fixed in qpidd-0.5.752581-13.el5
On RHEL4 you will need CXXFLAGS=-I/usr/include/qpid-boost as usual in order to compile the cpp test.
Reproduced on 0.5.752581-5
Verified on -13, both archs, both RHELs.
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.