Bug 1010388 - Verifying Network of ActiveMQ Brokers Using the ActiveMQ Console shows wrong information
Summary: Verifying Network of ActiveMQ Brokers Using the ActiveMQ Console shows wrong ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 1.2.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Julie
QA Contact: Alison Young
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-20 16:33 UTC by Nikhil Mone
Modified: 2018-12-02 15:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-07 23:59:12 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nikhil Mone 2013-09-20 16:33:16 UTC
Description of problem: 

Section : 5.8.4.4.2. Verifying Network of ActiveMQ Brokers Using the ActiveMQ Console shows wrong information. It should not list the ephemeral ports.

https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/1/html/Deployment_Guide/Verifying_Network_of_ActiveMQ_Brokers_Using_the_ActiveMQ_Console.html


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


How reproducible:

Create duplex connectors between 3 activemq brokers and then check "network.jsp"

Steps to Reproduce:

                        amq1
                      //    \\
                     //      \\
                  amq2 ===== amq3    

1. Create duplex connectors between 3 activemq brokers
2. Check "network.jsp"
3. You will only see :

Network Bridges

Remote Broker   Remote Address      Created By Duplex Messages Enqueued Messages Dequeued
activemq02.example.com tcp://172.16.14.13:61616 false          0                 0
activemq03.example.com tcp://172.16.14.15:61616 false             0                 0

Actual results:

                                                     Created  Messages  Messages
  Remote Broker                Remote Address          By     Enqueued  Dequeued
                                                     Duplex
  activemq2.example.com   tcp://192.168.59.163:61616 false    15        15
  activemq2.example.com   tcp://192.168.59.163:32827 true     15        15
  activemq3.example.com   tcp://192.168.59.147:41338 true     15        15
  activemq3.example.com   tcp://192.168.59.147:61616 false    15        15


Expected results:


                                                     Created  Messages  Messages
  Remote Broker                Remote Address          By     Enqueued  Dequeued
                                                     Duplex
  activemq2.example.com   tcp://192.168.59.163:61616 false    15        15
  activemq3.example.com   tcp://192.168.59.147:61616 false    15        15


Additional info:


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