Hide Forgot
Description of problem: 1. chapter 7.1. - Starting a Broker in a Cluster (page 32): The should also have identical ACL files and SASL databases.. s/The/They 2. chapter 7.2. - qpid-cluster (page 35) Let's connect to a cluster and display basic information about the cluser and its brokers. When you connect to the cluster using qpid-tool, you can use the host and port for any broker in the cluster. For instance, if a broker in the cluster is running on localhost on port 6664, you can start qpid-tool like this: This chapter is dedicated to qpid-cluster command not qpid-tool. s/qpid-tool/qpid-cluster (2 occurrences) s/cluser/cluster (1 occurrence) 3. chapter 7.3.2. - Failover and the Qpid Messaging API (page 36) ... a connection fails. . two dots at the end of the sentence. ...(i.e. messages whice were... s/whice/which 4. chapter 8.4. - The qpid-route Utility (page 41) The syntax of qpid-route is not up2date: - qpid-route [OPTIONS] list connections [<broker>] + qpid-route [OPTIONS] link add <dest-broker> <src-broker> + qpid-route [OPTIONS] link del <dest-broker> <src-broker> + qpid-route [OPTIONS] link list [<dest-broker>] 5. chapter 12.1. Using qpid-config (page 68) The example output of 'qpid-config queues' is not up2date The actual output looks like: Queue Name Attributes ====================================================================== qmfagent-16a3e0ab-03c0-4a96-a416-7d0bc336d5fd auto-del excl qmfagent-d7da3494-c52d-414d-a214-b662158f5edf auto-del excl qmfc-v2-hb-rh5_64.6212.1 auto-del excl --limit-policy=ring qmfc-v2-rh5_64.6212.1 auto-del excl qmfc-v2-ui-rh5_64.6212.1 auto-del excl --limit-policy=ring reply-rh5_64.6212.1 auto-del excl topic-rh5_64.6212.1 auto-del excl --limit-policy=ring 6. chapter 12.2. Using qpid-tool (page 69-70) command outputs not up2date step 3: # qpid-tool Management Tool for QPID qpid: list Summary of Objects by Type: Package Class Active Deleted ======================================================= org.apache.qpid.broker exchange 8 0 com.redhat.rhm.store store 1 0 org.apache.qpid.broker broker 1 0 org.apache.qpid.broker binding 16 12 org.apache.qpid.broker session 2 1 org.apache.qpid.broker connection 2 1 org.apache.qpid.broker vhost 1 0 org.apache.qpid.broker queue 6 5 org.apache.qpid.broker system 1 0 org.apache.qpid.broker subscription 6 5 step 4: 'list qpid.system' is now replaced with only 'list system' qpid: list system Object Summary: ID Created Destroyed Index ======================================================================== 167 07:34:13 - UUID('b3e2610e-5420-49ca-8306-dca812db647f') 7. chapter 12.3. - Using qpid-queue-stats (page 72) step 3: To view the statistic for a particular broker, use the qpid-view-stats.. s/qpid-view-stats/qpid-queue-stats Version-Release number of selected component (if applicable): Red Hat Enterprise MRG 1.3 - Messaging User Guide Revision 2.3 How reproducible: 100% Steps to Reproduce: n/a Actual results: Minor issues in Messaging UG Expected results: Update of Messaging UG Additional info: n/a
*** Bug 672991 has been marked as a duplicate of this bug. ***
Changes in revision 2.4, build Red_Hat_Enterprise_MRG-Messaging_User_Guide-1.3-web-en-US-2-4.el5 1. command line arguments. They should also have identical ACL files and SASL databases if these are used. 2. <para> Let's connect to a cluster and display basic information about the cluster and its brokers. When you connect to the cluster using <command>qpid-cluster</command>, you can use the host and port for any broker in the cluster. For instance, if a broker in the cluster is running on <filename>localhost</filename> on port 6664, you can start <command>qpid-cluster</command> like this: </para> 3. The Qpid Messaging API also supports automatic reconnection in the event a connection fails. Senders can also be configured to replay any in-doubt messages (i.e. messages which were sent but not acknowleged by the broker. See "Connection Options" and "Sender Capacity and Replay" in <citetitle>Programming in Apache Qpid</citetitle> for details. 4. qpid-route [OPTIONS] link add <dest-broker> <src-broker> qpid-route [OPTIONS] link del <dest-broker> <src-broker> qpid-route [OPTIONS] link list [<dest-broker>] 5. <screen> $ qpid-config queues Queue Name Attributes ====================================================================== qmfagent-16a3e0ab-03c0-4a96-a416-7d0bc336d5fd auto-del excl qmfagent-d7da3494-c52d-414d-a214-b662158f5edf auto-del excl qmfc-v2-hb-rh5_64.6212.1 auto-del excl --limit-policy=ring qmfc-v2-rh5_64.6212.1 auto-del excl qmfc-v2-ui-rh5_64.6212.1 auto-del excl --limit-policy=ring reply-rh5_64.6212.1 auto-del excl topic-rh5_64.6212.1 auto-del excl --limit-policy=ring </screen> 6.3 <screen> # qpid-tool Management Tool for QPID qpid: list Summary of Objects by Type: Package Class Active Deleted ======================================================= org.apache.qpid.broker exchange 8 0 com.redhat.rhm.store store 1 0 org.apache.qpid.broker broker 1 0 org.apache.qpid.broker binding 16 12 org.apache.qpid.broker session 2 1 org.apache.qpid.broker connection 2 1 org.apache.qpid.broker vhost 1 0 org.apache.qpid.broker queue 6 5 org.apache.qpid.broker system 1 0 org.apache.qpid.broker subscription 6 5 </screen> 6.4 <screen> qpid: list system Object Summary: ID Created Destroyed Index ======================================================================== 167 07:34:13 - UUID('b3e2610e-5420-49ca-8306-dca812db647f') </screen> 7. To view the statistics for a particular broker, use the <command>qpid-queue-stats</command> command and specify the broker.
Appropriate changes done in doc-stage: Red Hat Enterprise MRG 1.3 - Messaging User Guide Revision2.4 Waiting for rhm-docs package.
The issue has been fixed. Red Hat Enterprise MRG 1.3 - Messaging User Guide Revision2.4 VERIFIED