Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 960049

Summary: qpid-latency-test reports it cannot achieve desired sending rate every second measurement
Product: Red Hat Enterprise MRG Reporter: Frantisek Reznicek <freznice>
Component: qpid-cppAssignee: Gordon Sim <gsim>
Status: CLOSED ERRATA QA Contact: Irina Boverman <iboverma>
Severity: low Docs Contact:
Priority: low    
Version: 2.3CC: esammons, iboverma, jross, lzhaldyb
Target Milestone: 3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-cpp-0.22-4.el6, qpid-cpp-0.22-4.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 15:07:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frantisek Reznicek 2013-05-06 13:44:16 UTC 
Description of problem:

While testing bug 826630.
Qpid-latency-test reports it cannot achieve desired sending rate every second measurement.

Bug 826630 is fixed, except small piece that warnings that tool is not able to reach expected sending rate is displayed every second measurement:

# /usr/bin/qpid-latency-test  --size 1024 --rate 10000000 --tcp-nodelay --csv --prefetch=2000 --sync
10000000,0.225675,4.83135,1.76719
10000000,0.495089,5.31136,1.82483
WARNING: Desired send rate: 10000000, actual send rate: 4398
10000000,0.466957,3.53673,1.69877
10000000,0.48648,4.61519,1.73114
WARNING: Desired send rate: 10000000, actual send rate: 4500
10000000,0.197411,5.28223,1.78111
10000000,0.447307,6.29959,1.67699
WARNING: Desired send rate: 10000000, actual send rate: 4519
...

That may confuse users that half of the measurements reached the sending-rate.

It is just small detail and thus severity low.


Version-Release number of selected component (if applicable):
2.3 and later including qpid-cpp-0.22-1.el6

How reproducible:
100%

Steps to Reproduce:
1. service qpidd restart
2. qpid-latency-test  --size 1024 --rate 10 --tcp-nodelay --csv --prefetch=2000 --sync
   should cause no warnings
3. qpid-latency-test  --size 1024 --rate 10000000 --tcp-nodelay --csv --prefetch=2000 --sync
   should cause warnings each matching one measurement.
  
Actual results:
  Half warnings are reported.

Expected results:
  All warnings for all measurements not meeting requirements should be reported.

Additional info:
Comment 1 Gordon Sim 2013-05-27 17:07:41 UTC 
The rate at which the warning is emitted now matches the report frequency (note though that these are done on two different threads). Fixed upstream by http://svn.apache.org/viewvc?view=revision&revision=1486666.
Comment 3 errata-xmlrpc 2014-09-24 15:07:59 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