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

Bug 433035

Summary: fanout example doesn't fan-out
Product: Red Hat Enterprise MRG Reporter: Alan Conway <aconway>
Component: Messaging_Programming_ReferenceAssignee: Alan Conway <aconway>
Status: CLOSED CURRENTRELEASE QA Contact: Kim van der Riet <kim.vdriet>
Severity: low Docs Contact:
Priority: low    
Version: beta   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: B4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-17 19:47:52 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 Alan Conway 2008-02-15 19:55:33 UTC 
Description of problem:


The fanout example is poorly written, it does not actually demonstrate what the
fan-out exchange does.

The fanout exchange copies messages to every queue that is bound to it, however
the example only binds
a single queue, so there's nowhere to fan out to. The listeners all bind to the
same queue and compete
for messages. If there are just a few then they're likely to all end up on the
same consumer,
because the broker delivers messages in batches for higher throughput.

I've attached a modified listener.cpp that creates a private queue for each
listener. If you start multiple
listeners you'll see they all get all the messages.
Comment 1 Alan Conway 2008-02-15 21:03:08 UTC 
New example in revision 628151
Comment 2 Jonathan Robie 2008-05-17 19:47:52 UTC 
It does fan out now, in both Python and C++.

There is no fanout example in Java. We should fix that for GA.
Comment 3 Jonathan Robie 2008-05-20 18:09:51 UTC 
Closing - the Java part of this issue is recorded in
https://bugzilla.redhat.com/show_bug.cgi?id=433036.