An Exchange is a named entity within the Virtual Host which receives messages from producers and routes them to matching Queues within the Virtual Host.
The server provides a set of exchange types with each exchange type implementing a different routing algorithm. For details of how these exchanges types work see Section 4.3.2, “Exchange Types” below.
The server predeclares a number of exchange instances with names starting with "
amq.". These are defined in
Section 4.3.1, “Predeclared Exchanges”.
Applications can make use the pre-declared exchanges, or they may declare their own. The number of exchanges within a virtual host is limited only by resource constraints.
The behaviour when an exchange is unable to route a message to any queue is defined in Section 4.3.4, “Unrouteable Messages”
Exchange configuration is covered in Chapter 8, Exchanges.
Each virtual host pre-declares the following exchanges:
The conceptual "
default exchange" always exists, effectively a special instance of
direct exchange which uses the empty string as its name. All queues are automatically bound to it upon their creation
using the queue name as the binding key, and unbound upon their deletion. It is not possible to manually add or remove
bindings within this exchange.
Applications may not declare exchanges with names beginning with "
amq.". Such names are reserved for system use.
The following Exchange types are supported.
These exchange types are described in the following sub-sections.
The direct exchange type routes messages to queues based on an exact match between the routing key of the message, and the binding key used to bind the queue to the exchange. Additional filter rules may be specified using a binding argument specifying a JMS message selector.
This exchange type is often used to implement point to point messaging. When used in this manner, the normal convention is that the binding key matches the name of the queue. It is also possible to use this exchange type for multi-cast, in this case the same binding key is associated with many queues.
The figure above illustrates the operation of direct exchange type. The yellow messages published with the routing key
myqueue" match the binding key corresponding to queue "
myqueue" and so are routed there. The red
messages published with the routing key "
foo" match two bindings in the table so a copy of the message is
routed to both the "
bar1" and "
The routing key of the blue message matches no binding keys, so the message is unroutable. It is handled as described in Section 4.3.4, “Unrouteable Messages”.
This exchange type is used to support the classic publish/subscribe paradigm.
The topic exchange is capable of routing messages to queues based on wildcard matches between the routing key and the binding key pattern defined by the queue binding. Routing keys are formed from one or more words, with each word delimited by a full-stop (.). The pattern matching characters are the * and # symbols. The * symbol matches a single word and the # symbol matches zero or more words.
Additional filter rules may be specified using a binding argument specifying a JMS message selector.
The following three figures help explain how the topic exchange functions.
The figure above illustrates publishing messages with routing key "
weather". The exchange routes each
message to every bound queue whose binding key matches the routing key.
In the case illustrated, this means that each subscriber's queue receives every yellow message.
The figure above illustrates publishing messages with hierarchical routing keys. As before, the exchange routes each message to every bound queue whose binding key matches the routing key but as the binding keys contain wildcards, the wildcard rules described above apply.
In the case illustrated,
sub1 has received the red and green message as "
news.uk" and "
match binding key "
news.#". The red message has also gone to
sub3 as it's routing key
is matched exactly by "
news.uk" and by "
The routing key of the yellow message matches no binding keys, so the message is unroutable. It is handled as described in Section 4.3.4, “Unrouteable Messages”.
The figure above illustrates messages with properties published with routing key "
As before, the exchange routes each message to every bound queue whose binding key matches the routing key but as a JMS selector argument has been specified, the expression is evaluated against each matching message. Only messages whose message header values or properties match the expression are routed to the queue.
In the case illustrated,
sub1 has received the yellow and blue message as their property "
cause expression "
area in ('Forties', 'Cromarty')" to evaluate true. Similarly, the yellow message has also gone to
gale_alert as its property "
speed" causes expression "
speed > 7 and speed < 10"
to evaluate true.
The properties of purple message cause no expressions to evaluate true, so the message is unroutable. It is handled as described in Section 4.3.4, “Unrouteable Messages”.
The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key.
Filter rules may be specified using a binding argument specifying a JMS message selector.
The headers exchange type routes messages to queues based on header properties within the message. The message is passed to a queue if the header properties of the message satisfy the x-match expression specified by the binding arguments with which the queue was bound.
Binding arguments are used by certain exchange types to further filter messages.
The binding argument
x-filter-jms-selector specifies a JMS selector conditional expression. The expression
is written in terms of message header and message property names. If the expression evaluates to true, the message is routed to the queue.
This type of binding argument is understood by exchange types direct, topic and fanout..
The binding argument
x-match is understood by exchange type headers. It can take two values, dictating how the
rest of the name value pairs are treated during matching.
allimplies that all the other pairs must match the headers property of a message for that message to be routed (i.e. an AND match)
implies that the message should be routed if any of the fields in the headers property match one of the fields in the arguments table (i.e. an OR match)
A field in the bind arguments matches a field in the message if either the field in the bind arguments has no value and a field of the same name is present in the message headers or if the field in the bind arguments has a value and a field of the same name exists in the message headers and has that same value.
If an exchange is unable to route a message to any queues, the Broker will:
 This is a Qpid specific extension.
Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners