|Summary:||ttl units not correct|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Rafael H. Schloming <rafaels>|
|Component:||python-qpid||Assignee:||Rafael H. Schloming <rafaels>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||MRG Quality Engineering <mrgqe-bugs>|
|Version:||6.0||CC:||bche, gsim, jneedle, syeghiay, tross|
|Fixed In Version:||python-qpid-0.7.946106-5.el6||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-11-15 14:43:20 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||612615|
Description Rafael H. Schloming 2010-07-08 16:25:59 UTC
+++ This bug was initially created as a clone of Bug #612615 +++ Description of problem: The Message API defines the ttl field as a float measuring seconds. The protocol uses milliseconds, and the API implementation is not properly converting. How reproducible: 100% Steps to Reproduce: 1. Publish a message with the ttl specified in seconds. 2. Check the protocol trace. Actual results: The value measured in seconds is directly put on the wire. Expected results: The value should first be converted to milliseconds.
Comment 1 Gordon Sim 2010-07-08 16:28:32 UTC
This becomes very hard to change after it is released, so I'd like to request this as an exception. The change is very contained and the risk is low.
Comment 2 Rafael H. Schloming 2010-07-09 13:32:33 UTC
I'd like to get this change into the next snapshot (Snapshot 8). I'm ready to respin, just waiting for approval.
Comment 5 firstname.lastname@example.org 2010-11-15 14:43:20 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.