Bug 459269 - C++ client consumes 100% CPU when idle (RHEL4)
Summary: C++ client consumes 100% CPU when idle (RHEL4)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.0
Hardware: i386
OS: Linux
urgent
urgent
Target Milestone: 1.0.1
: ---
Assignee: messaging-bugs
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On: 456991
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-15 14:58 UTC by Ted Ross
Modified: 2011-08-12 16:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-06 18:59:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0867 0 normal SHIPPED_LIVE Red Hat Enterprise MRG bug fix and enhancement update 2008-10-06 18:58:51 UTC

Description Ted Ross 2008-08-15 14:58:48 UTC
+++ This bug was initially created as a clone of Bug #456991 +++

The C++ client consumes 100% of the CPU (one core on multi-core systems) even
when idle, waiting for messages on a subscription.

To reproduce, simply run the "listener" program in the C++ "direct" example (you
will need to run "declare-queues" first).  While the program waits for incoming
messages, measure the CPU usage of the "lt-listener" process.

Note that this problem only appears to occur on 32-bit architectures.

--- Additional comment from gsim on 2008-07-29 08:30:36 EDT ---

I believe this is a result of the fact that Condition::wait(FAR_FUTURE) returns
immediately with ETIMEDOUT.


--- Additional comment from gsim on 2008-07-29 09:50:31 EDT ---

Fixed on qpid.0-10 by r680695 and on trunk by r680691.

Comment 2 Frantisek Reznicek 2008-09-09 16:45:53 UTC
There is now RHTS automated test MRG_Messaging/qpid_cpp_client_load_bz456991 which shows that bug has been fixed. (ON_QA->VERIFIED)

Comment 4 errata-xmlrpc 2008-10-06 18:59:21 UTC
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/RHBA-2008-0867.html


Note You need to log in before you can comment on or make changes to this bug.