On 03/24/2014 05:52 AM, Pavel Moravec wrote:
Hi all,
I am trying to play with Dispatch Router but dont understand its addressing. In 
particular:

1) Having a router listening on port say 10000, how to point qdstat to it?

$ tools/qdstat -a -b "amqp://0.0.0.0:10000/"
Failed: MessengerException - [-2]: unable to connect to amqp:/#: 
getaddrinfo(amqp, ): Name or service not known
$ tools/qdstat -a -r "amqp://0.0.0.0:10000/"
No response from router amqp://0.0.0.0:10000/ after timeout
$ tools/qdstat -a -r "amqp://0.0.0.0:10000/local/$management" -t 1
No response from router amqp://0.0.0.0:10000/local/ after timeout
$ ..

I'll see if I can clarify the usage of the arguments in the man page and help.

Use "-b 0.0.0.0:10000". The -b argument is the host portion of the address being used to contact the server.

2) Having a mobile listener on address "my-address" on router A inter-connected 
to router B, what tool and what address to use to send messages there? I tried qpid-send 
from qpid broker with addresses:

"amqp://0.0.0.0/my-address"
"/my-address"

but apparently qpid-send is stuck to "message.to/message.routingKey" schema.

[1] refers to send.py and recv.py but I cant locate them in either Dispatch or 
Qpid broker sources.

Thanks in advance for hints.

The send.py and recv.py referred to come from the Proton project.

You can also use "spout" and "drain" from Qpid:

$ drain --connection-options {protocol:amqp1.0} -b 0.0.0.0:10000 -f my_address $ spout --connection-options {protocol:amqp1.0} -b 0.0.0.0:10000 my_address

The qpid-send.py from Qpid unly uses AMQP 0-10, so that won't be compatible with Dispatch.

-Ted


Kind regards,
Pavel

[1] http://qpid.apache.org/releases/qpid-dispatch-0.1/notes.html

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



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

Reply via email to