You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2008/03/20 01:00:24 UTC
[jira] Created: (QPID-864) Modify the Fanout example to reflect the
fanout functionality
Modify the Fanout example to reflect the fanout functionality
-------------------------------------------------------------
Key: QPID-864
URL: https://issues.apache.org/jira/browse/QPID-864
Project: Qpid
Issue Type: Improvement
Components: Java Tests
Affects Versions: M3
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: M3
The current fanout example cannot be used to demonstrate the functionality of the fanout exchange.
The C++ and python examples are already modified to run multiple instances.
You should be able to start multiple instances of the Listener and Consumer that would create and bind a queue to the fanout exchange and receive all messages published to it.
In order to use pure JMS the Listener and Consumer classes are modified to take a JNDI name (of a queue bound to the fanout exchange) from the command line. The fanout.properties defines 3 such queues. The verify script currently starts 3 listeners for the fanout example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-864) Modify the Fanout example to reflect
the fanout functionality
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580628#action_12580628 ]
Rajith Attapattu commented on QPID-864:
---------------------------------------
This issue has a fix in r639090 of the trunk.
> Modify the Fanout example to reflect the fanout functionality
> -------------------------------------------------------------
>
> Key: QPID-864
> URL: https://issues.apache.org/jira/browse/QPID-864
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M3
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: M3
>
>
> The current fanout example cannot be used to demonstrate the functionality of the fanout exchange.
> The C++ and python examples are already modified to run multiple instances.
> You should be able to start multiple instances of the Listener and Consumer that would create and bind a queue to the fanout exchange and receive all messages published to it.
> In order to use pure JMS the Listener and Consumer classes are modified to take a JNDI name (of a queue bound to the fanout exchange) from the command line. The fanout.properties defines 3 such queues. The verify script currently starts 3 listeners for the fanout example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (QPID-864) Modify the Fanout example to reflect the
fanout functionality
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu closed QPID-864.
---------------------------------
> Modify the Fanout example to reflect the fanout functionality
> -------------------------------------------------------------
>
> Key: QPID-864
> URL: https://issues.apache.org/jira/browse/QPID-864
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M3
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: M3
>
>
> The current fanout example cannot be used to demonstrate the functionality of the fanout exchange.
> The C++ and python examples are already modified to run multiple instances.
> You should be able to start multiple instances of the Listener and Consumer that would create and bind a queue to the fanout exchange and receive all messages published to it.
> In order to use pure JMS the Listener and Consumer classes are modified to take a JNDI name (of a queue bound to the fanout exchange) from the command line. The fanout.properties defines 3 such queues. The verify script currently starts 3 listeners for the fanout example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-864) Modify the Fanout example to reflect
the fanout functionality
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-864.
-----------------------------------
Resolution: Fixed
This has been added and verified.
Closing issue
> Modify the Fanout example to reflect the fanout functionality
> -------------------------------------------------------------
>
> Key: QPID-864
> URL: https://issues.apache.org/jira/browse/QPID-864
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M3
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: M3
>
>
> The current fanout example cannot be used to demonstrate the functionality of the fanout exchange.
> The C++ and python examples are already modified to run multiple instances.
> You should be able to start multiple instances of the Listener and Consumer that would create and bind a queue to the fanout exchange and receive all messages published to it.
> In order to use pure JMS the Listener and Consumer classes are modified to take a JNDI name (of a queue bound to the fanout exchange) from the command line. The fanout.properties defines 3 such queues. The verify script currently starts 3 listeners for the fanout example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.