THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| No Format |
|---|
-------------------------------------------------+ +------------------------
localhost:10002 source broker | | destination brokerlocalhost:10001
| |
+-------------+ | | +-------------+
| | | | | |
| | global.# ---------------+ | | | |
| amq.topic |-----------> private queue |--------------->| amq.topic |
| | ---------------+ | | | |
| | | | | |
+-------------+ | | +-------------+
| |
| |
-------------------------------------------------+ +------------------------
|
Queue Routes
Pull vs. Push Routes
qpid-route Summary and Options
Caveats, Limitations, and Things to Avoid
...
A queue route causes the destination broker to create a subscription to a pre-existing, possibly shared, queue on the source broker. There's no requirement that the queue be bound to any particular exchange. Queue routes can be used to connect exchanges of different names and/or types. They can also be used to distribute or balance traffic across multiple destination brokers.
Queue routes are created and deleted using the qpid-route queue add and qpid-route queue del commands respectively. The following example creates a static queue route to a public queue called "public" that feeds the amq.fanout exchange on the destination:
Create a queue on the source broker:
| No Format |
|---|
$ qpid-config -a localhost:10002 add queue public
|
Create a queue route to the new queue
| No Format |
|---|
$ qpid-route queue add localhost:10001 localhost:10002 amq.fanout public
|
Pull vs. Push Routes
qpid-route Summary and Options
Caveats, Limitations, and Things to Avoid
Redundant Paths
Lack of Flow Control
Example Scenarios
Using QPID to bridge disjoint IP networks
...