Bug 452128
| Summary: | Feature: message throttling | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Sergei Vorobiev <sergei.vorobiev> |
| Component: | qpid-cpp | Assignee: | Andrew Stitcher <astitcher> |
| Status: | CLOSED ERRATA | QA Contact: | Kim van der Riet <kim.vdriet> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 1.0 | CC: | cctrieloff, freznice, gsim, iboverma |
| Target Milestone: | 1.1.1 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-04-21 16:16:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sergei Vorobiev
2008-06-19 15:13:13 UTC
to also control an AMQP client connection to the maximum rate for messages sent over specific AMQP session to a broker (i.e. limit all the taffic from one client, no matter how many sessions). Client session throttling has now been implemented in qpid C++ broker and client: It is configured by setting a configuration parameter in qpidd. The new command line argument is "--max-session-rate" This imposes a limit on the number of messages transferred per second from the client to the broker on every session. This functionality can be tested by (for example) running the broker with a specified session rate: qpidd --auth no --max-session-rate 200 Then by running perftest against this broker and seeing that the send rate from client to broker is just less than this rate. The feature has been implemented, tested using qpidd and perftest with and without --max-session-rate qpidd option. Done on RHEL 4.7 / 5.3 i386 / x86_64 on packages: qpidd-0.4.744917-1.el4/5 ->VERIFIED 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. http://rhn.redhat.com/errata/RHEA-2009-0434.html |