AMQP 0-9-1 Complete Reference Guide

connection

Work with socket connections.

The connection class provides methods for a client to establish a network connection to a server, and for both peers to operate the connection thereafter.

Class Grammar:

      connection          = open-connection *use-connection close-connection
      open-connection     = C:protocol-header
                            S:START C:START-OK
                            *challenge
                            S:TUNE C:TUNE-OK
                            C:OPEN S:OPEN-OK
      challenge           = S:SECURE C:SECURE-OK
      use-connection      = *channel
      close-connection    = C:CLOSE S:CLOSE-OK
                          / S:CLOSE C:CLOSE-OK
    

Methods

start(

octet version-major, octet version-minor, peer-properties server-properties, longstr mechanisms, longstr locales) ➔ start-ok

Start connection negotiation.

This method starts the connection negotiation process by telling the client the protocol version that the server proposes, along with a list of security mechanisms which the client can use for authentication.

• If the server cannot support the protocol specified in the protocol header, it MUST respond with a valid protocol header and then close the socket connection.
• The server MUST provide a protocol version that is lower than or equal to that requested by the client in the protocol header.
• If the client cannot handle the protocol version suggested by the server it MUST close the socket connection without sending any further data.

Parameters:

octet version-major

The major version number can take any value from 0 to 99 as defined in the AMQP specification.

octet version-minor

The minor version number can take any value from 0 to 99 as defined in the AMQP specification.

peer-properties server-properties

Server properties.

• The properties SHOULD contain at least these fields: "host", specifying the server host name or address, "product", giving the name of the server product, "version", giving the name of the server version, "platform", giving the name of the operating system, "copyright", if appropriate, and "information", giving other general information.

longstr mechanisms

A list of the security mechanisms that the server supports, delimited by spaces.

longstr locales

A list of the message locales that the server supports, delimited by spaces. The locale defines the language in which the server will send reply texts.

• The server MUST support at least the en_US locale.

start-ok(

peer-properties client-properties, shortstr mechanism, longstr response, shortstr locale)

Select security mechanism and locale.

This method selects a SASL security mechanism.

Parameters:

peer-properties client-properties

Client properties.

• The properties SHOULD contain at least these fields: "product", giving the name of the client product, "version", giving the name of the client version, "platform", giving the name of the operating system, "copyright", if appropriate, and "information", giving other general information.

shortstr mechanism

A single security mechanisms selected by the client, which must be one of those specified by the server.

• The client SHOULD authenticate using the highest-level security profile it can handle from the list provided by the server.
• If the mechanism field does not contain one of the security mechanisms proposed by the server in the Start method, the server MUST close the connection without sending any further data.

longstr response

A block of opaque data passed to the security mechanism. The contents of this data are defined by the SASL security mechanism.

shortstr locale

A single message locale selected by the client, which must be one of those specified by the server.

secure(

longstr challenge) ➔ secure-ok

Security mechanism challenge.

The SASL protocol works by exchanging challenges and responses until both peers have received sufficient information to authenticate each other. This method challenges the client to provide more information.

Parameters:

longstr challenge

Challenge information, a block of opaque binary data passed to the security mechanism.

secure-ok(

longstr response)

Security mechanism response.

This method attempts to authenticate, passing a block of SASL data for the security mechanism at the server side.

Parameters:

longstr response

A block of opaque data passed to the security mechanism. The contents of this data are defined by the SASL security mechanism.

tune(

short channel-max, long frame-max, short heartbeat) ➔ tune-ok

Propose connection tuning parameters.

This method proposes a set of connection configuration values to the client. The client can accept and/or adjust these.

Parameters:

short channel-max

Specifies highest channel number that the server permits. Usable channel numbers are in the range 1..channel-max. Zero indicates no specified limit.

long frame-max

The largest frame size that the server proposes for the connection, including frame header and end-byte. The client can negotiate a lower value. Zero means that the server does not impose any specific limit but may reject very large frames if it cannot allocate resources for them.

• Until the frame-max has been negotiated, both peers MUST accept frames of up to frame-min-size octets large, and the minimum negotiated value for frame-max is also frame-min-size.

short heartbeat

The delay, in seconds, of the connection heartbeat that the server wants. Zero means the server does not want a heartbeat.

tune-ok(

short channel-max, long frame-max, short heartbeat)

Negotiate connection tuning parameters.

This method sends the client's connection tuning parameters to the server. Certain fields are negotiated, others provide capability information.

Parameters:

short channel-max

The maximum total number of channels that the client will use per connection.

• If the client specifies a channel max that is higher than the value provided by the server, the server MUST close the connection without attempting a negotiated close. The server may report the error in some fashion to assist implementors.

long frame-max

The largest frame size that the client and server will use for the connection. Zero means that the client does not impose any specific limit but may reject very large frames if it cannot allocate resources for them. Note that the frame-max limit applies principally to content frames, where large contents can be broken into frames of arbitrary size.

• Until the frame-max has been negotiated, both peers MUST accept frames of up to frame-min-size octets large, and the minimum negotiated value for frame-max is also frame-min-size.
• If the client specifies a frame max that is higher than the value provided by the server, the server MUST close the connection without attempting a negotiated close. The server may report the error in some fashion to assist implementors.

short heartbeat

The delay, in seconds, of the connection heartbeat that the client wants. Zero means the client does not want a heartbeat.

open(

path virtual-host, shortstr reserved-1, bit reserved-2) ➔ open-ok

Open connection to virtual host.

This method opens a connection to a virtual host, which is a collection of resources, and acts to separate multiple application domains within a server. The server may apply arbitrary limits per virtual host, such as the number of each type of entity that may be used, per connection and/or in total.

Parameters:

path virtual-host

The name of the virtual host to work with.

• If the server supports multiple virtual hosts, it MUST enforce a full separation of exchanges, queues, and all associated entities per virtual host. An application, connected to a specific virtual host, MUST NOT be able to access resources of another virtual host.
• The server SHOULD verify that the client has permission to access the specified virtual host.

shortstr reserved-1

bit reserved-2

open-ok(

shortstr reserved-1)

Signal that connection is ready.

This method signals to the client that the connection is ready for use.

Parameters:

shortstr reserved-1

close(

reply-code reply-code, reply-text reply-text, class-id class-id, method-id method-id) ➔ close-ok

Request a connection close.

This method indicates that the sender wants to close the connection. This may be due to internal conditions (e.g. a forced shut-down) or due to an error handling a specific method, i.e. an exception. When a close is due to an exception, the sender provides the class and method id of the method which caused the exception.

• After sending this method, any received methods except Close and Close-OK MUST be discarded. The response to receiving a Close after sending Close must be to send Close-Ok.

Parameters:

reply-code reply-code

reply-text reply-text

class-id class-id

When the close is provoked by a method exception, this is the class of the method.

method-id method-id

When the close is provoked by a method exception, this is the ID of the method.

close-ok(

)

Confirm a connection close.

This method confirms a Connection.Close method and tells the recipient that it is safe to release resources for the connection and close the socket.

• A peer that detects a socket closure without having received a Close-Ok handshake method SHOULD log the error.

blocked(

shortstr reason)

Indicate that connection is blocked.

This method indicates that a connection has been blocked and does not accept new publishes.

Parameters:

shortstr reason

The reason the connection was blocked.

unblocked(

)

Indicate that connection is unblocked.

This method indicates that a connection has been unblocked and now accepts publishes.

update-secret(

longstr new-secret, shortstr reason) ➔ update-secret-ok

Update secret.

This method updates the secret used to authenticate this connection. It is used when secrets have an expiration date and need to be renewed, like OAuth 2 tokens.

Parameters:

longstr new-secret

The new secret.

shortstr reason

The reason for the secret update.

update-secret-ok(

)

Update secret response.

This method confirms the updated secret is valid.

channel

Work with channels.

The channel class provides methods for a client to establish a channel to a server and for both peers to operate the channel thereafter.

Class Grammar:

      channel             = open-channel *use-channel close-channel
      open-channel        = C:OPEN S:OPEN-OK
      use-channel         = C:FLOW S:FLOW-OK
                          / S:FLOW C:FLOW-OK
                          / functional-class
      close-channel       = C:CLOSE S:CLOSE-OK
                          / S:CLOSE C:CLOSE-OK
    

Methods

open(

shortstr reserved-1) ➔ open-ok

Open a channel for use.

This method opens a channel to the server.

• The client MUST NOT use this method on an already-opened channel. Error code: channel-error

Parameters:

shortstr reserved-1

open-ok(

longstr reserved-1)

Signal that the channel is ready.

This method signals to the client that the channel is ready for use.

Parameters:

longstr reserved-1

flow(

bit active) ➔ flow-ok

Enable/disable flow from peer.

This method asks the peer to pause or restart the flow of content data sent by a consumer. This is a simple flow-control mechanism that a peer can use to avoid overflowing its queues or otherwise finding itself receiving more messages than it can process. Note that this method is not intended for window control. It does not affect contents returned by Basic.Get-Ok methods.

• When a new channel is opened, it is active (flow is active). Some applications assume that channels are inactive until started. To emulate this behaviour a client MAY open the channel, then pause it.
• When sending content frames, a peer SHOULD monitor the channel for incoming methods and respond to a Channel.Flow as rapidly as possible.
• A peer MAY use the Channel.Flow method to throttle incoming content data for internal reasons, for example, when exchanging data over a slower connection.
• The peer that requests a Channel.Flow method MAY disconnect and/or ban a peer that does not respect the request. This is to prevent badly-behaved clients from overwhelming a server.

Parameters:

bit active

If 1, the peer starts sending content frames. If 0, the peer stops sending content frames.

flow-ok(

bit active)

Confirm a flow method.

Confirms to the peer that a flow command was received and processed.

Parameters:

bit active

Confirms the setting of the processed flow method: 1 means the peer will start sending or continue to send content frames; 0 means it will not.

close(

reply-code reply-code, reply-text reply-text, class-id class-id, method-id method-id) ➔ close-ok

Request a channel close.

This method indicates that the sender wants to close the channel. This may be due to internal conditions (e.g. a forced shut-down) or due to an error handling a specific method, i.e. an exception. When a close is due to an exception, the sender provides the class and method id of the method which caused the exception.

• After sending this method, any received methods except Close and Close-OK MUST be discarded. The response to receiving a Close after sending Close must be to send Close-Ok.

Parameters:

reply-code reply-code

reply-text reply-text

class-id class-id

When the close is provoked by a method exception, this is the class of the method.

method-id method-id

When the close is provoked by a method exception, this is the ID of the method.

close-ok(

)

Confirm a channel close.

This method confirms a Channel.Close method and tells the recipient that it is safe to release resources for the channel.

• A peer that detects a socket closure without having received a Channel.Close-Ok handshake method SHOULD log the error.

exchange

Work with exchanges.

Exchanges match and distribute messages across queues. Exchanges can be configured in the server or declared at runtime.

Class Grammar:

      exchange            = C:DECLARE  S:DECLARE-OK
                          / C:DELETE   S:DELETE-OK
                          / C:BIND     S:BIND-OK
                          / C:UNBIND   S:UNBIND-OK
    

• The server MUST implement these standard exchange types: fanout, direct.
• The server SHOULD implement these standard exchange types: topic, headers.
• The server MUST, in each virtual host, pre-declare an exchange instance for each standard exchange type that it implements, where the name of the exchange instance, if defined, is "amq." followed by the exchange type name. The server MUST, in each virtual host, pre-declare at least two direct exchange instances: one named "amq.direct", the other with no public name that serves as a default exchange for Publish methods.
• The server MUST pre-declare a direct exchange with no public name to act as the default exchange for content Publish methods and for default queue bindings.
• The server MUST NOT allow clients to access the default exchange except by specifying an empty exchange name in the Queue.Bind and content Publish methods.
• The server MAY implement other exchange types as wanted.

Methods

declare(

short reserved-1, exchange-name exchange, shortstr type, bit passive, bit durable, bit auto-delete, bit internal, no-wait no-wait, table arguments) ➔ declare-ok

Verify exchange exists, create if needed.

This method creates an exchange if it does not already exist, and if the exchange exists, verifies that it is of the correct and expected class.

• The server SHOULD support a minimum of 16 exchanges per virtual host and ideally, impose no limit except as defined by available resources.

Parameters:

short reserved-1

exchange-name exchange

• Exchange names starting with "amq." are reserved for pre-declared and standardised exchanges. The client MAY declare an exchange starting with "amq." if the passive option is set, or the exchange already exists. Error code: access-refused
• The exchange name consists of a non-empty sequence of these characters: letters, digits, hyphen, underscore, period, or colon. Error code: precondition-failed

shortstr type

Each exchange belongs to one of a set of exchange types implemented by the server. The exchange types define the functionality of the exchange - i.e. how messages are routed through it. It is not valid or meaningful to attempt to change the type of an existing exchange.

• Exchanges cannot be redeclared with different types. The client MUST not attempt to redeclare an existing exchange with a different type than used in the original Exchange.Declare method. Error code: not-allowed
• The client MUST NOT attempt to declare an exchange with a type that the server does not support. Error code: command-invalid

bit passive

If set, the server will reply with Declare-Ok if the exchange already exists with the same name, and raise an error if not. The client can use this to check whether an exchange exists without modifying the server state. When set, all other method fields except name and no-wait are ignored. A declare with both passive and no-wait has no effect. Arguments are compared for semantic equivalence.

• If set, and the exchange does not already exist, the server MUST raise a channel exception with reply code 404 (not found).
• If not set and the exchange exists, the server MUST check that the existing exchange has the same values for type, durable, and arguments fields. The server MUST respond with Declare-Ok if the requested exchange matches these fields, and MUST raise a channel exception if not.

bit durable

If set when creating a new exchange, the exchange will be marked as durable. Durable exchanges remain active when a server restarts. Non-durable exchanges (transient exchanges) are purged if/when a server restarts.

• The server MUST support both durable and transient exchanges.

bit auto-delete

If set, the exchange is deleted when all queues have finished using it.

• The server SHOULD allow for a reasonable delay between the point when it determines that an exchange is not being used (or no longer used), and the point when it deletes the exchange. At the least it must allow a client to create an exchange and then bind a queue to it, with a small but non-zero delay between these two actions.
• The server MUST ignore the auto-delete field if the exchange already exists.

bit internal

If set, the exchange may not be used directly by publishers, but only when bound to other exchanges. Internal exchanges are used to construct wiring that is not visible to applications.

no-wait no-wait

table arguments

A set of arguments for the declaration. The syntax and semantics of these arguments depends on the server implementation.

declare-ok(

)

Confirm exchange declaration.

This method confirms a Declare method and confirms the name of the exchange, essential for automatically-named exchanges.

delete(

short reserved-1, exchange-name exchange, bit if-unused, no-wait no-wait) ➔ delete-ok

Delete an exchange.

This method deletes an exchange. When an exchange is deleted all queue bindings on the exchange are cancelled.

Parameters:

short reserved-1

exchange-name exchange

• The client MUST NOT attempt to delete an exchange that does not exist. Error code: not-found

bit if-unused

If set, the server will only delete the exchange if it has no queue bindings. If the exchange has queue bindings the server does not delete it but raises a channel exception instead.

• The server MUST NOT delete an exchange that has bindings on it, if the if-unused field is true. Error code: precondition-failed

no-wait no-wait

delete-ok(

)

Confirm deletion of an exchange.

This method confirms the deletion of an exchange.

bind(

short reserved-1, exchange-name destination, exchange-name source, shortstr routing-key, no-wait no-wait, table arguments) ➔ bind-ok

Bind exchange to an exchange.

This method binds an exchange to an exchange.

• A server MUST allow and ignore duplicate bindings - that is, two or more bind methods for a specific exchanges, with identical arguments - without treating these as an error.
• A server MUST allow cycles of exchange bindings to be created including allowing an exchange to be bound to itself.
• A server MUST not deliver the same message more than once to a destination exchange, even if the topology of exchanges and bindings results in multiple (even infinite) routes to that exchange.

Parameters:

short reserved-1

exchange-name destination

Specifies the name of the destination exchange to bind.

• A client MUST NOT be allowed to bind a non-existent destination exchange. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.

exchange-name source

Specifies the name of the source exchange to bind.

• A client MUST NOT be allowed to bind a non-existent source exchange. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.

shortstr routing-key

Specifies the routing key for the binding. The routing key is used for routing messages depending on the exchange configuration. Not all exchanges use a routing key - refer to the specific exchange documentation.

no-wait no-wait

table arguments

A set of arguments for the binding. The syntax and semantics of these arguments depends on the exchange class.

bind-ok(

)

Confirm bind successful.

This method confirms that the bind was successful.

unbind(

short reserved-1, exchange-name destination, exchange-name source, shortstr routing-key, no-wait no-wait, table arguments) ➔ unbind-ok

Unbind an exchange from an exchange.

This method unbinds an exchange from an exchange.

• If a unbind fails, the server MUST raise a connection exception.

Parameters:

short reserved-1

exchange-name destination

Specifies the name of the destination exchange to unbind.

• The client MUST NOT attempt to unbind an exchange that does not exist from an exchange. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.

exchange-name source

Specifies the name of the source exchange to unbind.

• The client MUST NOT attempt to unbind an exchange from an exchange that does not exist. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.

shortstr routing-key

Specifies the routing key of the binding to unbind.

no-wait no-wait

table arguments

Specifies the arguments of the binding to unbind.

unbind-ok(

)

Confirm unbind successful.

This method confirms that the unbind was successful.

queue

Work with queues.

Queues store and forward messages. Queues can be configured in the server or created at runtime. Queues must be attached to at least one exchange in order to receive messages from publishers.

Class Grammar:

      queue               = C:DECLARE  S:DECLARE-OK
                          / C:BIND     S:BIND-OK
                          / C:UNBIND   S:UNBIND-OK
                          / C:PURGE    S:PURGE-OK
                          / C:DELETE   S:DELETE-OK
    

Methods

declare(

short reserved-1, queue-name queue, bit passive, bit durable, bit exclusive, bit auto-delete, no-wait no-wait, table arguments) ➔ declare-ok

Declare queue, create if needed.

This method creates or checks a queue. When creating a new queue the client can specify various properties that control the durability of the queue and its contents, and the level of sharing for the queue.

• The server MUST create a default binding for a newly-declared queue to the default exchange, which is an exchange of type 'direct' and use the queue name as the routing key.
• The server SHOULD support a minimum of 256 queues per virtual host and ideally, impose no limit except as defined by available resources.

Parameters:

short reserved-1

queue-name queue

• The queue name MAY be empty, in which case the server MUST create a new queue with a unique generated name and return this to the client in the Declare-Ok method.
• Queue names starting with "amq." are reserved for pre-declared and standardised queues. The client MAY declare a queue starting with "amq." if the passive option is set, or the queue already exists. Error code: access-refused
• The queue name can be empty, or a sequence of these characters: letters, digits, hyphen, underscore, period, or colon. Error code: precondition-failed

bit passive

If set, the server will reply with Declare-Ok if the queue already exists with the same name, and raise an error if not. The client can use this to check whether a queue exists without modifying the server state. When set, all other method fields except name and no-wait are ignored. A declare with both passive and no-wait has no effect. Arguments are compared for semantic equivalence.

• The client MAY ask the server to assert that a queue exists without creating the queue if not. If the queue does not exist, the server treats this as a failure. Error code: not-found
• If not set and the queue exists, the server MUST check that the existing queue has the same values for durable, exclusive, auto-delete, and arguments fields. The server MUST respond with Declare-Ok if the requested queue matches these fields, and MUST raise a channel exception if not.

bit durable

If set when creating a new queue, the queue will be marked as durable. Durable queues remain active when a server restarts. Non-durable queues (transient queues) are purged if/when a server restarts. Note that durable queues do not necessarily hold persistent messages, although it does not make sense to send persistent messages to a transient queue.

• The server MUST recreate the durable queue after a restart.
• The server MUST support both durable and transient queues.

bit exclusive

Exclusive queues may only be accessed by the current connection, and are deleted when that connection closes. Passive declaration of an exclusive queue by other connections are not allowed.

• The server MUST support both exclusive (private) and non-exclusive (shared) queues.
• The client MAY NOT attempt to use a queue that was declared as exclusive by another still-open connection. Error code: resource-locked

bit auto-delete

If set, the queue is deleted when all consumers have finished using it. The last consumer can be cancelled either explicitly or because its channel is closed. If there was no consumer ever on the queue, it won't be deleted. Applications can explicitly delete auto-delete queues using the Delete method as normal.

• The server MUST ignore the auto-delete field if the queue already exists.

no-wait no-wait

table arguments

A set of arguments for the declaration. The syntax and semantics of these arguments depends on the server implementation.

declare-ok(

queue-name queue, message-count message-count, long consumer-count)

Confirms a queue definition.

This method confirms a Declare method and confirms the name of the queue, essential for automatically-named queues.

Parameters:

queue-name queue

Reports the name of the queue. If the server generated a queue name, this field contains that name.

message-count message-count

long consumer-count

Reports the number of active consumers for the queue. Note that consumers can suspend activity (Channel.Flow) in which case they do not appear in this count.

bind(

short reserved-1, queue-name queue, exchange-name exchange, shortstr routing-key, no-wait no-wait, table arguments) ➔ bind-ok

Bind queue to an exchange.

This method binds a queue to an exchange. Until a queue is bound it will not receive any messages. In a classic messaging model, store-and-forward queues are bound to a direct exchange and subscription queues are bound to a topic exchange.

• A server MUST allow ignore duplicate bindings - that is, two or more bind methods for a specific queue, with identical arguments - without treating these as an error.
• A server MUST not deliver the same message more than once to a queue, even if the queue has multiple bindings that match the message.
• The server MUST allow a durable queue to bind to a transient exchange.
• Bindings of durable queues to durable exchanges are automatically durable and the server MUST restore such bindings after a server restart.
• The server SHOULD support at least 4 bindings per queue, and ideally, impose no limit except as defined by available resources.

Parameters:

short reserved-1

queue-name queue

Specifies the name of the queue to bind.

• The client MUST either specify a queue name or have previously declared a queue on the same channel Error code: not-found
• The client MUST NOT attempt to bind a queue that does not exist. Error code: not-found

exchange-name exchange

Name of the exchange to bind to.

• A client MUST NOT be allowed to bind a queue to a non-existent exchange. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.

shortstr routing-key

Specifies the routing key for the binding. The routing key is used for routing messages depending on the exchange configuration. Not all exchanges use a routing key - refer to the specific exchange documentation. If the queue name is empty, the server uses the last queue declared on the channel. If the routing key is also empty, the server uses this queue name for the routing key as well. If the queue name is provided but the routing key is empty, the server does the binding with that empty routing key. The meaning of empty routing keys depends on the exchange implementation.

• If a message queue binds to a direct exchange using routing key K and a publisher sends the exchange a message with routing key R, then the message MUST be passed to the message queue if K = R.

no-wait no-wait

table arguments

A set of arguments for the binding. The syntax and semantics of these arguments depends on the exchange class.

bind-ok(

)

Confirm bind successful.

This method confirms that the bind was successful.

unbind(

short reserved-1, queue-name queue, exchange-name exchange, shortstr routing-key, table arguments) ➔ unbind-ok

Unbind a queue from an exchange.

This method unbinds a queue from an exchange.

• If a unbind fails, the server MUST raise a connection exception.

Parameters:

short reserved-1

queue-name queue

Specifies the name of the queue to unbind.

• The client MUST either specify a queue name or have previously declared a queue on the same channel Error code: not-found
• The client MUST NOT attempt to unbind a queue that does not exist. Error code: not-found

exchange-name exchange

The name of the exchange to unbind from.

• The client MUST NOT attempt to unbind a queue from an exchange that does not exist. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.

shortstr routing-key

Specifies the routing key of the binding to unbind.

table arguments

Specifies the arguments of the binding to unbind.

unbind-ok(

)

Confirm unbind successful.

This method confirms that the unbind was successful.

purge(

short reserved-1, queue-name queue, no-wait no-wait) ➔ purge-ok

Purge a queue.

This method removes all messages from a queue which are not awaiting acknowledgment.

• The server MUST NOT purge messages that have already been sent to a client but not yet acknowledged.
• The server MAY implement a purge queue or log that allows system administrators to recover accidentally-purged messages. The server SHOULD NOT keep purged messages in the same storage spaces as the live messages since the volumes of purged messages may get very large.

Parameters:

short reserved-1

queue-name queue

Specifies the name of the queue to purge.

• The client MUST either specify a queue name or have previously declared a queue on the same channel Error code: not-found
• The client MUST NOT attempt to purge a queue that does not exist. Error code: not-found

no-wait no-wait

purge-ok(

message-count message-count)

Confirms a queue purge.

This method confirms the purge of a queue.

Parameters:

message-count message-count

Reports the number of messages purged.

delete(

short reserved-1, queue-name queue, bit if-unused, bit if-empty, no-wait no-wait) ➔ delete-ok

Delete a queue.

This method deletes a queue. When a queue is deleted any pending messages are sent to a dead-letter queue if this is defined in the server configuration, and all consumers on the queue are cancelled.

• The server SHOULD use a dead-letter queue to hold messages that were pending on a deleted queue, and MAY provide facilities for a system administrator to move these messages back to an active queue.

Parameters:

short reserved-1

queue-name queue

Specifies the name of the queue to delete.

• The client MUST either specify a queue name or have previously declared a queue on the same channel Error code: not-found
• The client MUST NOT attempt to delete a queue that does not exist. Error code: not-found

bit if-unused

If set, the server will only delete the queue if it has no consumers. If the queue has consumers the server does does not delete it but raises a channel exception instead.

• The server MUST NOT delete a queue that has consumers on it, if the if-unused field is true. Error code: precondition-failed

bit if-empty

If set, the server will only delete the queue if it has no messages.

• The server MUST NOT delete a queue that has messages on it, if the if-empty field is true. Error code: precondition-failed

no-wait no-wait

delete-ok(

message-count message-count)

Confirm deletion of a queue.

This method confirms the deletion of a queue.

Parameters:

message-count message-count

Reports the number of messages deleted.

basic

Work with basic content.

The Basic class provides methods that support an industry-standard messaging model.

Class Grammar:

      basic               = C:QOS S:QOS-OK
                          / C:CONSUME S:CONSUME-OK
                          / C:CANCEL S:CANCEL-OK
                          / C:PUBLISH content
                          / S:RETURN content
                          / S:DELIVER content
                          / C:GET ( S:GET-OK content / S:GET-EMPTY )
                          / C:ACK
                          / S:ACK
                          / C:REJECT
                          / C:NACK
                          / S:NACK
                          / C:RECOVER-ASYNC
                          / C:RECOVER S:RECOVER-OK
    

• The server SHOULD respect the persistent property of basic messages and SHOULD make a best-effort to hold persistent basic messages on a reliable storage mechanism.
• The server MUST NOT discard a persistent basic message in case of a queue overflow.
• The server MAY use the Channel.Flow method to slow or stop a basic message publisher when necessary.
• The server MAY overflow non-persistent basic messages to persistent storage.
• The server MAY discard or dead-letter non-persistent basic messages on a priority basis if the queue size exceeds some configured limit.
• The server MUST implement at least 2 priority levels for basic messages, where priorities 0-4 and 5-9 are treated as two distinct levels.
• The server MAY implement up to 10 priority levels.
• The server MUST deliver messages of the same priority in order irrespective of their individual persistence.
• The server MUST support un-acknowledged delivery of Basic content, i.e. consumers with the no-ack field set to TRUE.
• The server MUST support explicitly acknowledged delivery of Basic content, i.e. consumers with the no-ack field set to FALSE.

Fields

Methods

qos(

long prefetch-size, short prefetch-count, bit global) ➔ qos-ok

Specify quality of service.

This method requests a specific quality of service. The QoS can be specified for the current channel or for all channels on the connection. The particular properties and semantics of a qos method always depend on the content class semantics. Though the qos method could in principle apply to both peers, it is currently meaningful only for the server.

Parameters:

long prefetch-size

The client can request that messages be sent in advance so that when the client finishes processing a message, the following message is already held locally, rather than needing to be sent down the channel. Prefetching gives a performance improvement. This field specifies the prefetch window size in octets. The server will send a message in advance if it is equal to or smaller in size than the available prefetch size (and also falls into other prefetch limits). May be set to zero, meaning "no specific limit", although other prefetch limits may still apply. The prefetch-size is ignored if the no-ack option is set.

• The server MUST ignore this setting when the client is not processing any messages - i.e. the prefetch size does not limit the transfer of single messages to a client, only the sending in advance of more messages while the client still has one or more unacknowledged messages.

short prefetch-count

Specifies a prefetch window in terms of whole messages. This field may be used in combination with the prefetch-size field; a message will only be sent in advance if both prefetch windows (and those at the channel and connection level) allow it. The prefetch-count is ignored if the no-ack option is set.

• The server may send less data in advance than allowed by the client's specified prefetch windows but it MUST NOT send more.

bit global

RabbitMQ has reinterpreted this field. The original specification said: "By default the QoS settings apply to the current channel only. If this field is set, they are applied to the entire connection." Instead, RabbitMQ takes global=false to mean that the QoS settings should apply per-consumer (for new consumers on the channel; existing ones being unaffected) and global=true to mean that the QoS settings should apply per-channel.

qos-ok(

)

Confirm the requested qos.

This method tells the client that the requested QoS levels could be handled by the server. The requested QoS applies to all active consumers until a new QoS is defined.

consume(

short reserved-1, queue-name queue, consumer-tag consumer-tag, no-local no-local, no-ack no-ack, bit exclusive, no-wait no-wait, table arguments) ➔ consume-ok

Start a queue consumer.

This method asks the server to start a "consumer", which is a transient request for messages from a specific queue. Consumers last as long as the channel they were declared on, or until the client cancels them.

• The server SHOULD support at least 16 consumers per queue, and ideally, impose no limit except as defined by available resources.

Parameters:

short reserved-1

queue-name queue

Specifies the name of the queue to consume from.

consumer-tag consumer-tag

Specifies the identifier for the consumer. The consumer tag is local to a channel, so two clients can use the same consumer tags. If this field is empty the server will generate a unique tag.

• The client MUST NOT specify a tag that refers to an existing consumer. Error code: not-allowed
• The consumer tag is valid only within the channel from which the consumer was created. I.e. a client MUST NOT create a consumer in one channel and then use it in another. Error code: not-allowed

no-local no-local

no-ack no-ack

bit exclusive

Request exclusive consumer access, meaning only this consumer can access the queue.

• The client MAY NOT gain exclusive access to a queue that already has active consumers. Error code: access-refused

no-wait no-wait

table arguments

A set of arguments for the consume. The syntax and semantics of these arguments depends on the server implementation.

consume-ok(

consumer-tag consumer-tag)

Confirm a new consumer.

The server provides the client with a consumer tag, which is used by the client for methods called on the consumer at a later stage.

Parameters:

consumer-tag consumer-tag

Holds the consumer tag specified by the client or provided by the server.

cancel(

consumer-tag consumer-tag, no-wait no-wait) ➔ cancel-ok

End a queue consumer.

This method cancels a consumer. This does not affect already delivered messages, but it does mean the server will not send any more messages for that consumer. The client may receive an arbitrary number of messages in between sending the cancel method and receiving the cancel-ok reply. It may also be sent from the server to the client in the event of the consumer being unexpectedly cancelled (i.e. cancelled for any reason other than the server receiving the corresponding basic.cancel from the client). This allows clients to be notified of the loss of consumers due to events such as queue deletion. Note that as it is not a MUST for clients to accept this method from the server, it is advisable for the broker to be able to identify those clients that are capable of accepting the method, through some means of capability negotiation.

• If the queue does not exist the server MUST ignore the cancel method, so long as the consumer tag is valid for that channel.

Parameters:

consumer-tag consumer-tag

no-wait no-wait

cancel-ok(

consumer-tag consumer-tag)

Confirm a cancelled consumer.

This method confirms that the cancellation was completed.

Parameters:

consumer-tag consumer-tag

publish(

short reserved-1, exchange-name exchange, shortstr routing-key, bit mandatory, bit immediate)

Publish a message.

This method publishes a message to a specific exchange. The message will be routed to queues as defined by the exchange configuration and distributed to any active consumers when the transaction, if any, is committed.

Parameters:

short reserved-1

exchange-name exchange

Specifies the name of the exchange to publish to. The exchange name can be empty, meaning the default exchange. If the exchange name is specified, and that exchange does not exist, the server will raise a channel exception.

• The client MUST NOT attempt to publish a content to an exchange that does not exist. Error code: not-found
• The server MUST accept a blank exchange name to mean the default exchange.
• If the exchange was declared as an internal exchange, the server MUST raise a channel exception with a reply code 403 (access refused).
• The exchange MAY refuse basic content in which case it MUST raise a channel exception with reply code 540 (not implemented).

shortstr routing-key

Specifies the routing key for the message. The routing key is used for routing messages depending on the exchange configuration.

bit mandatory

This flag tells the server how to react if the message cannot be routed to a queue. If this flag is set, the server will return an unroutable message with a Return method. If this flag is zero, the server silently drops the message.

• The server SHOULD implement the mandatory flag.

bit immediate

This flag tells the server how to react if the message cannot be routed to a queue consumer immediately. If this flag is set, the server will return an undeliverable message with a Return method. If this flag is zero, the server will queue the message, but with no guarantee that it will ever be consumed.

• The server SHOULD implement the immediate flag.

return(

reply-code reply-code, reply-text reply-text, exchange-name exchange, shortstr routing-key)

Return a failed message.

This method returns an undeliverable message that was published with the "immediate" flag set, or an unroutable message published with the "mandatory" flag set. The reply code and text provide information about the reason that the message was undeliverable.

Parameters:

reply-code reply-code

reply-text reply-text

exchange-name exchange

Specifies the name of the exchange that the message was originally published to. May be empty, meaning the default exchange.

shortstr routing-key

Specifies the routing key name specified when the message was published.

deliver(

consumer-tag consumer-tag, delivery-tag delivery-tag, redelivered redelivered, exchange-name exchange, shortstr routing-key)

Notify the client of a consumer message.

This method delivers a message to the client, via a consumer. In the asynchronous message delivery model, the client starts a consumer using the Consume method, then the server responds with Deliver methods as and when messages arrive for that consumer.

• The server SHOULD track the number of times a message has been delivered to clients and when a message is redelivered a certain number of times - e.g. 5 times - without being acknowledged, the server SHOULD consider the message to be unprocessable (possibly causing client applications to abort), and move the message to a dead letter queue.

Parameters:

consumer-tag consumer-tag

delivery-tag delivery-tag

redelivered redelivered

exchange-name exchange

Specifies the name of the exchange that the message was originally published to. May be empty, indicating the default exchange.

shortstr routing-key

Specifies the routing key name specified when the message was published.

get(

short reserved-1, queue-name queue, no-ack no-ack) ➔ get-ok | get-empty

Direct access to a queue.

This method provides a direct access to the messages in a queue using a synchronous dialogue that is designed for specific types of application where synchronous functionality is more important than performance.

Parameters:

short reserved-1

queue-name queue

Specifies the name of the queue to get a message from.

no-ack no-ack

get-ok(

delivery-tag delivery-tag, redelivered redelivered, exchange-name exchange, shortstr routing-key, message-count message-count)

Provide client with a message.

This method delivers a message to the client following a get method. A message delivered by 'get-ok' must be acknowledged unless the no-ack option was set in the get method.

Parameters:

delivery-tag delivery-tag

redelivered redelivered

exchange-name exchange

Specifies the name of the exchange that the message was originally published to. If empty, the message was published to the default exchange.

shortstr routing-key

Specifies the routing key name specified when the message was published.

message-count message-count

get-empty(

shortstr reserved-1)

Indicate no messages available.

This method tells the client that the queue has no messages available for the client.

Parameters:

shortstr reserved-1

ack(

delivery-tag delivery-tag, bit multiple)

Acknowledge one or more messages.

When sent by the client, this method acknowledges one or more messages delivered via the Deliver or Get-Ok methods. When sent by server, this method acknowledges one or more messages published with the Publish method on a channel in confirm mode. The acknowledgement can be for a single message or a set of messages up to and including a specific message.

Parameters:

delivery-tag delivery-tag

bit multiple

If set to 1, the delivery tag is treated as "up to and including", so that multiple messages can be acknowledged with a single method. If set to zero, the delivery tag refers to a single message. If the multiple field is 1, and the delivery tag is zero, this indicates acknowledgement of all outstanding messages.

• A message MUST not be acknowledged more than once. The receiving peer MUST validate that a non-zero delivery-tag refers to a delivered message, and raise a channel exception if this is not the case. On a transacted channel, this check MUST be done immediately and not delayed until a Tx.Commit. Error code: precondition-failed

reject(

delivery-tag delivery-tag, bit requeue)

Reject an incoming message.

This method allows a client to reject a message. It can be used to interrupt and cancel large incoming messages, or return untreatable messages to their original queue.

• The server SHOULD be capable of accepting and process the Reject method while sending message content with a Deliver or Get-Ok method. I.e. the server should read and process incoming methods while sending output frames. To cancel a partially-send content, the server sends a content body frame of size 1 (i.e. with no data except the frame-end octet).
• The server SHOULD interpret this method as meaning that the client is unable to process the message at this time.
• The client MUST NOT use this method as a means of selecting messages to process.

Parameters:

delivery-tag delivery-tag

bit requeue

If requeue is true, the server will attempt to requeue the message. If requeue is false or the requeue attempt fails the messages are discarded or dead-lettered.

• The server MUST NOT deliver the message to the same client within the context of the current channel. The recommended strategy is to attempt to deliver the message to an alternative consumer, and if that is not possible, to move the message to a dead-letter queue. The server MAY use more sophisticated tracking to hold the message on the queue and redeliver it to the same client at a later stage.

recover-async(

bit requeue)

Redeliver unacknowledged messages.

This method asks the server to redeliver all unacknowledged messages on a specified channel. Zero or more messages may be redelivered. This method is deprecated in favour of the synchronous Recover/Recover-Ok.

• The server MUST set the redelivered flag on all messages that are resent.

Parameters:

bit requeue

If this field is zero, the message will be redelivered to the original recipient. If this bit is 1, the server will attempt to requeue the message, potentially then delivering it to an alternative subscriber.

recover(

bit requeue)

Redeliver unacknowledged messages.

This method asks the server to redeliver all unacknowledged messages on a specified channel. Zero or more messages may be redelivered. This method replaces the asynchronous Recover.

• The server MUST set the redelivered flag on all messages that are resent.

Parameters:

bit requeue

If this field is zero, the message will be redelivered to the original recipient. If this bit is 1, the server will attempt to requeue the message, potentially then delivering it to an alternative subscriber.

recover-ok(

)

Confirm recovery.

This method acknowledges a Basic.Recover method.

nack(

delivery-tag delivery-tag, bit multiple, bit requeue)

Reject one or more incoming messages.

This method allows a client to reject one or more incoming messages. It can be used to interrupt and cancel large incoming messages, or return untreatable messages to their original queue. This method is also used by the server to inform publishers on channels in confirm mode of unhandled messages. If a publisher receives this method, it probably needs to republish the offending messages.

• The server SHOULD be capable of accepting and processing the Nack method while sending message content with a Deliver or Get-Ok method. I.e. the server should read and process incoming methods while sending output frames. To cancel a partially-send content, the server sends a content body frame of size 1 (i.e. with no data except the frame-end octet).
• The server SHOULD interpret this method as meaning that the client is unable to process the message at this time.
• The client MUST NOT use this method as a means of selecting messages to process.
• A client publishing messages to a channel in confirm mode SHOULD be capable of accepting and somehow handling the Nack method.

Parameters:

delivery-tag delivery-tag

bit multiple

If set to 1, the delivery tag is treated as "up to and including", so that multiple messages can be rejected with a single method. If set to zero, the delivery tag refers to a single message. If the multiple field is 1, and the delivery tag is zero, this indicates rejection of all outstanding messages.

• A message MUST not be rejected more than once. The receiving peer MUST validate that a non-zero delivery-tag refers to an unacknowledged, delivered message, and raise a channel exception if this is not the case. Error code: precondition-failed

bit requeue

If requeue is true, the server will attempt to requeue the message. If requeue is false or the requeue attempt fails the messages are discarded or dead-lettered. Clients receiving the Nack methods should ignore this flag.

• The server MUST NOT deliver the message to the same client within the context of the current channel. The recommended strategy is to attempt to deliver the message to an alternative consumer, and if that is not possible, to move the message to a dead-letter queue. The server MAY use more sophisticated tracking to hold the message on the queue and redeliver it to the same client at a later stage.

tx

Work with transactions.

The Tx class allows publish and ack operations to be batched into atomic units of work. The intention is that all publish and ack requests issued within a transaction will complete successfully or none of them will. Servers SHOULD implement atomic transactions at least where all publish or ack requests affect a single queue. Transactions that cover multiple queues may be non-atomic, given that queues can be created and destroyed asynchronously, and such events do not form part of any transaction. Further, the behaviour of transactions with respect to the immediate and mandatory flags on Basic.Publish methods is not defined.

Class Grammar:

      tx                  = C:SELECT S:SELECT-OK
                          / C:COMMIT S:COMMIT-OK
                          / C:ROLLBACK S:ROLLBACK-OK
    

• Applications MUST NOT rely on the atomicity of transactions that affect more than one queue.
• Applications MUST NOT rely on the behaviour of transactions that include messages published with the immediate option.
• Applications MUST NOT rely on the behaviour of transactions that include messages published with the mandatory option.

Methods

select(

) ➔ select-ok

Select standard transaction mode.

This method sets the channel to use standard transactions. The client must use this method at least once on a channel before using the Commit or Rollback methods.

select-ok(

)

Confirm transaction mode.

This method confirms to the client that the channel was successfully set to use standard transactions.

commit(

) ➔ commit-ok

Commit the current transaction.

This method commits all message publications and acknowledgments performed in the current transaction. A new transaction starts immediately after a commit.

• The client MUST NOT use the Commit method on non-transacted channels. Error code: precondition-failed

commit-ok(

)

Confirm a successful commit.

This method confirms to the client that the commit succeeded. Note that if a commit fails, the server raises a channel exception.

rollback(

) ➔ rollback-ok

Abandon the current transaction.

This method abandons all message publications and acknowledgments performed in the current transaction. A new transaction starts immediately after a rollback. Note that unacked messages will not be automatically redelivered by rollback; if that is required an explicit recover call should be issued.

• The client MUST NOT use the Rollback method on non-transacted channels. Error code: precondition-failed

rollback-ok(

)

Confirm successful rollback.

This method confirms to the client that the rollback succeeded. Note that if an rollback fails, the server raises a channel exception.

confirm

Work with confirms.

The Confirm class allows publishers to put the channel in confirm mode and subsequently be notified when messages have been handled by the broker. The intention is that all messages published on a channel in confirm mode will be acknowledged at some point. By acknowledging a message the broker assumes responsibility for it and indicates that it has done something it deems reasonable with it. Unroutable mandatory or immediate messages are acknowledged right after the Basic.Return method. Messages are acknowledged when all queues to which the message has been routed have either delivered the message and received an acknowledgement (if required), or enqueued the message (and persisted it if required). Published messages are assigned ascending sequence numbers, starting at 1 with the first Confirm.Select method. The server confirms messages by sending Basic.Ack methods referring to these sequence numbers.

Class Grammar:

      confirm            = C:SELECT S:SELECT-OK
    

• The server MUST acknowledge all messages received after the channel was put into confirm mode.
• The server MUST acknowledge a message only after it was properly handled by all the queues it was delivered to.
• The server MUST acknowledge an unroutable mandatory or immediate message only after it sends the Basic.Return.
• No guarantees are made as to how soon a message is acknowledged. Applications SHOULD NOT make assumptions about this.

Methods

select(

no-wait nowait) ➔ select-ok

.

This method sets the channel to use publisher acknowledgements. The client can only use this method on a non-transactional channel.

Parameters:

no-wait nowait

select-ok(

)

.

This method confirms to the client that the channel was successfully set to use publisher acknowledgements.