[ 
https://issues.apache.org/jira/browse/DISPATCH-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947489#comment-14947489
 ] 

Ganesh Murthy commented on DISPATCH-156:
----------------------------------------

Hi Pavel,
    I used 

{code}
listener {
    addr: 0.0.0.0
    port: amqp
    authenticatePeer: no
}
{code}

Then I started dispatch router and ran simple_recv.py (just to register a 
receiver). I see this on the console
{code}
[gmurthy@localhost dispatch]$ qdrouterd -c etc/qdrouterd.conf 
Wed Oct  7 15:46:29 2015 SERVER (info) Container Name: Qpid.Dispatch.Router.A
Wed Oct  7 15:46:29 2015 ROUTER (info) Router started in Standalone mode
Wed Oct  7 15:46:29 2015 AGENT (info) Activating management agent on $management
Wed Oct  7 15:46:29 2015 ROUTER (info) In-Process Address Registered: 
$management
Wed Oct  7 15:46:29 2015 ROUTER (info) In-Process Address Registered: 
$management
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/closest/ 
phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_SINGLE 
bias=QD_SCHEMA_FIXEDADDRESS_BIAS_CLOSEST
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/multicast/ 
phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_MULTIPLE
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/queue/ 
phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_SINGLE 
bias=QD_SCHEMA_FIXEDADDRESS_BIAS_CLOSEST
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/queue/ 
phase=1 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_SINGLE 
bias=QD_SCHEMA_FIXEDADDRESS_BIAS_CLOSEST
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/unicast 
phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_SINGLE 
bias=QD_SCHEMA_FIXEDADDRESS_BIAS_CLOSEST
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/exclusive 
phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_SINGLE 
bias=QD_SCHEMA_FIXEDADDRESS_BIAS_CLOSEST
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/broadcast 
phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_MULTIPLE
Wed Oct  7 15:46:29 2015 ROUTER (info) Configured Address: prefix=/ phase=0 
fanout=QD_SCHEMA_FIXEDADDRESS_FANOUT_MULTIPLE
Wed Oct  7 15:46:29 2015 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp 
role=normal
Wed Oct  7 15:46:29 2015 SERVER (info) Operational, 1 Threads Running
Wed Oct  7 15:46:31 2015 ROUTER (info) Registered local address=examples 
phase=0 
{code}

Then, I ran *qdstat -b localhost:5672 -c* and I see this
{code}
[gmurthy@localhost tools]$ qdstat -b localhost:5672 -c
Connections
  host                         container                             role    
dir  security     authentication
  
=============================================================================================================
  localhost.localdomain:41824  9721e3aa-a919-44fe-955f-703d4580ee2c  normal  in 
  no-security  no-auth
  localhost.localdomain:41827  91d5c9cf-10bf-4a47-ba92-78b440b8d9bc  normal  in 
  no-security  no-auth
{code}

Running *qdstat -b 0.0.0.0:5672 -c* yields the same results as well.

I have attached my *qdrouterd.conf* for your perusal. Thanks

> [dispatch-tools] qdstat fails to connect to localhost via IPv4
> --------------------------------------------------------------
>
>                 Key: DISPATCH-156
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-156
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 0.4
>            Reporter: Pavel Moravec
>            Assignee: Ganesh Murthy
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: qdrouterd.conf
>
>
> Calling "qdstat -b localhost:5672 -c" tries to communicate to the dispatch 
> router via IPv6 only. If that fails, no attempt on IPv4 is done.
> Just for reference, /etc/hosts has:
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to