Hi Adel, the router doesn't support the "store and forward" mechanism itself so you need to connect a broker in order to store messages.
The addresses you see are all related to the management endpoint for example or reply address for the requests which comes from tools (like qdstat, qdmanage, ...). Some other addresses are used for routers communication. No one of this "support" something like a storing feature, it's just an address related to an AMQP node. By the way, you asked if "Do we need a broker to send/receive messages?". It's true only if you want store feature. Otherwise you can have a receiver and a sender exchanging messages directly through the router. It means that if receiver is offline and not connected to the router, the sender doesn't receive credits in order to send messages until the receiver will be online on the same address (so as I said messages can't be stored waiting for a receiver coming online). Thanks, Paolo Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin : paolopatierno Blog : DevExperience > From: [email protected] > To: [email protected] > Subject: [Qpid dispatch router] Do we need a broker to send/receive messages? > Date: Thu, 28 Jul 2016 16:17:55 +0200 > > Hello, > > Out of curiosity, Can I send/receive messages with a queue defined directly > on the dispatch router or do I need to have a real instance of a broker > connected to that dispatcher? > > I am asking because it seems that the dispatch router has by default some > "Addresses" used for internal communication and I was wondering if I could > create an "address" of a type queue and use it directly without adding > connectors. > > Router Addresses > class addr phs distrib in-proc local remote cntnr > in out thru to-proc from-proc > > =============================================================================================================== > local $_management_internal closest 1 0 0 0 > 0 0 0 0 0 > local $displayname closest 1 0 0 0 > 0 0 0 0 0 > mobile $management 0 closest 1 0 0 0 > 3 0 0 3 0 > local $management closest 1 0 0 0 > 0 0 0 0 0 > local temp.9yqNIIHanFkSZbe closest 0 1 0 0 > 0 0 0 0 0 > > > Regards, > Adel >
