Bug 705414

Summary: TTL overflow
Product: Red Hat Enterprise MRG Reporter: Andy Goldstein <agoldste>
Component: qpid-cppAssignee: Gordon Sim <gsim>
Status: CLOSED ERRATA QA Contact: Leonid Zhaldybin <lzhaldyb>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.3CC: esammons, gsim, jross, lzhaldyb, mtoth
Target Milestone: 3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-cpp-server-0.12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 15:02:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 698367    

Description Andy Goldstein 2011-05-17 15:47:15 UTC
Description of problem: when setting a message's TTL to Duration::FOREVER, the calculated expiration time overflows, resulting in the message being expired essentially immediately.

See https://issues.apache.org/jira/browse/QPID-3222 for more details.

Comment 1 Gordon Sim 2011-05-17 15:50:45 UTC
Fixed upstream: http://svn.apache.org/viewvc?view=rev&rev=1096751

Comment 2 Leonid Zhaldybin 2013-07-30 13:22:18 UTC
Tested on RHEL6.4 (both i386 and x86_64).

Packages used for testing:

python-qpid-0.22-4.el6
python-qpid-qmf-0.22-7.el6
qpid-cpp-client-0.22-8.el6
qpid-cpp-client-devel-0.22-8.el6
qpid-cpp-client-devel-docs-0.22-8.el6
qpid-cpp-client-rdma-0.22-8.el6
qpid-cpp-client-ssl-0.22-8.el6
qpid-cpp-server-0.22-8.el6
qpid-cpp-server-devel-0.22-8.el6
qpid-cpp-server-ha-0.22-8.el6
qpid-cpp-server-rdma-0.22-8.el6
qpid-cpp-server-ssl-0.22-8.el6
qpid-cpp-server-store-0.22-8.el6
qpid-cpp-server-xml-0.22-8.el6
qpid-java-client-0.22-5.el6
qpid-java-common-0.22-5.el6
qpid-java-example-0.22-5.el6
qpid-proton-c-0.4-2.2.el6
qpid-qmf-0.22-7.el6
qpid-qmf-devel-0.22-7.el6
qpid-tools-0.22-3.el6

-> VERIFIED

Comment 4 errata-xmlrpc 2014-09-24 15:02:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1296.html