Address Mapping

This is the master reference for how the embedded KubeMQ AMQP 1.0 connector maps an AMQP 1.0 terminus address to a KubeMQ (pattern, channel) pair — which server link role results from a peer's source/target choice, and the channel-naming rules, anonymous-routing behavior, and RPC reply token that each pattern carries.

Address grammar

address       = [ "/" ] ( prefixed-node | bare-node )
prefixed-node = pattern-prefix channel
pattern-prefix = "queues/" | "events/" | "events-store/"
               | "commands/" | "queries/" | "responses/"
bare-node     = channel                 ; no "/" — resolved via node-cap hint or DefaultPattern
channel       = 1*255 VCHAR             ; connector charset rules (see Channel validation)

• The leading slash is optional. The resolver strips at most one leading / before matching, so queues/orders and /queues/orders resolve identically.
• Each pattern prefix includes its trailing slash ("events/", "events-store/"), so the prefix match is unambiguous.
• A null/empty address is not an error in itself — on a server-receiver link it selects the anonymous terminus (see below); on a dynamic terminus it asks the server to mint a node.

The master mapping table

The pattern is taken from the address prefix. The server link role is the inverse of the peer's role: a peer receiver attaches against a source address (the server sends), and a peer sender attaches against a target address (the server receives).

Notes carried by the table:

• The same <pattern>/<channel> resolves to the same KubeMQ channel regardless of link direction — only the server role (and therefore the authorization check) differs.
• commands/, queries/, and responses/ are RPC machinery. A requester's reply link is a dynamic node, not a <pattern>/<channel> address (see below).
• responses/<RequestID> is valid only as a server-receiver link (the peer is a sender writing the reply). A receiver attach against responses/ is rejected with amqp:not-allowed.

Longest-prefix discipline

events-store/ and events/ share a common stem. The resolver matches events-store/ before events/, so events-store/audit is never mis-classified as the events pattern with channel store/audit. The prefix checks run in this fixed order:

events-store/   — checked FIRST
queues/
events/
commands/
queries/
responses/

A bare address that still contains a / but matches no recognized prefix is an unknown prefix → amqp:not-found — a bare KubeMQ channel may use . segments but never the reserved / separator.

Special rows — bare, dynamic, anonymous, responses

Server role and authorization

The peer's link role and the chosen terminus side together fix the server role and the permission required at attach:

The pattern → authorization resource map treats events-store as the resource events_store, and commands / queries as commands / queries. See Authentication.

Channel validation (connector charset)

The channel component (everything after the pattern prefix) is validated by a connector charset rule that is stricter than the array-layer validation, so a channel that passes here always passes downstream. Any violation maps to amqp:not-found (a bad address is "not found"):

There is no vhost / virtual host. The OPEN hostname field is accepted but ignored — the address space is flat and global. For AMQP 0-9-1 interop the channel convention is queues/amqp.<vhost>.<queue> (a naming convention, not a real vhost).

Quick examples

Related