Bug 1128654 - nextReceiver() with IMMEDIATE duration always returns null
Summary: nextReceiver() with IMMEDIATE duration always returns null
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 2.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: 2.5.5
: ---
Assignee: Gordon Sim
QA Contact: Zdenek Kraus
Depends On: 1128653
Blocks: 1140368 1140369
TreeView+ depends on / blocked
Reported: 2014-08-11 10:04 UTC by Gordon Sim
Modified: 2018-12-09 18:19 UTC (History)
8 users (show)

Fixed In Version: qpid-cpp-0.18-29
Doc Type: Bug Fix
Doc Text:
It was discovered that calling Session::nextReceiver() with a duration of IMMEDIATE always returned null, even if there were incoming messages waiting. This bug, introduced as part of the fix for bug 958895 in the 2.3.3 release, resulted in incoming messages never being received. The fix allows for messages to be returned even if there is no waiting period. Messages are now properly delivered.
Clone Of: 1128653
Last Closed: 2014-10-22 16:34:21 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Apache JIRA QPID-5985 None None None Never
Red Hat Product Errata RHBA-2014:1682 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 2 update 2014-10-22 20:34:01 UTC

Description Gordon Sim 2014-08-11 10:04:08 UTC
+++ This bug was initially created as a clone of Bug #1128653 +++

Description of problem:

Calling Session::nextReceiver() with a duration of IMMEDIATE will always return null, even if there are incoming messages waiting. This bug was introduced as part of the fix for bug 958895.

Version-Release number of selected component (if applicable):

qpid-0.24, mrg 2.3.3, qpid-0.28

How reproducible:


Steps to Reproduce:
1. put some messages in a queue
2. have a program that creates a receiver for the queue, sets a non-zero capacity, then loops until nextReceiver(Duration::IMMEDIATE returns a non-null receiver), e.g.:

   Receiver next;
   while (ssn.nextReceiver(next, Duration::IMMEDIATE)) {}

Actual results:

The while loop never returns, even though there are messages on the queue

Expected results:

The while loop exits once the broker has sent out (a) message(s)

Additional info:

It should be pointed out that using nextReceiver() with a Duration::IMMEDIATE value in this way is inefficient and rather odd. A much better solution would be to specify some non-zero timeout. This would avoid the cpu usage of a 'busy wait' while in no way either increasing the actual time until the next receiver is obtained or the maximum theoretical time.

Using nextReceiver() with a non-zero timeout also avoids this bug.

Comment 2 Gordon Sim 2014-08-11 11:28:44 UTC
Fixed upstream: https://svn.apache.org/r1617256

Comment 4 Gordon Sim 2014-08-14 12:50:22 UTC
The commit above fixes one regression but introduces another. Need https://svn.apache.org/r1617924 also from upstream.

Comment 8 Zdenek Kraus 2014-09-23 17:19:19 UTC
Tested on RHEL6 RHEL5 i686 x86_64, with following packages:


Comment 10 errata-xmlrpc 2014-10-22 16:34:21 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.


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