Bug 612615 - ttl units not correct
Summary: ttl units not correct
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid   
(Show other bugs)
Version: Development
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.3
: ---
Assignee: Rafael H. Schloming
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 612632
TreeView+ depends on / blocked
 
Reported: 2010-07-08 15:46 UTC by Rafael H. Schloming
Modified: 2014-12-01 23:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 612632 (view as bug list)
Environment:
Last Closed: 2013-02-25 10:45:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rafael H. Schloming 2010-07-08 15:46:09 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.