rabbitmq
RabbitMQ AMQP Reply Codes
Numeric reply codes returned by RabbitMQ in channel.close and connection.close frames, as defined by the AMQP 0-9-1 protocol specification. Reply codes indicate the reason a channel or connection was closed, covering success, soft errors (channel-level), and hard errors (connection-level).
19 codes
2xx Success 1 codes
3xx Redirection 4 codes
- 311 content-too-large The message content is larger than the maximum size permitted by the broker. The client must reduce the size of the message before retrying.
- 312 no-route The client published a message with the mandatory flag set, but the broker could not find a matching queue binding and the message was unroutable. The message is returned to the publisher.
- 313 no-consumers The client published a message with the immediate flag set, but no consumers on the matching queue were ready to accept the delivery. The message is returned to the publisher.
- 320 connection-forced The broker is closing the connection due to an operator request, such as a server shutdown or administrative action. This is a hard error that closes the entire connection.
4xx Client error 5 codes
- 402 invalid-path The path provided in a connection.open frame is invalid or not known to the virtual host. This is a hard error and the connection is closed.
- 403 access-refused The client attempted an operation that it is not authorised to perform. This may be due to missing permissions on a resource such as a queue, exchange, or virtual host.
- 404 not-found The named resource (queue, exchange, or binding) does not exist. The client referenced an entity that the broker cannot locate.
- 405 resource-locked The client attempted to work with a resource that is exclusively locked by another connection or channel. For example, declaring a queue as exclusive when another connection already holds it.
- 406 precondition-failed A precondition set by the client was not met by the broker. Common causes include declaring a queue or exchange with properties that conflict with an existing resource of the same name.
5xx Server error 9 codes
- 501 frame-error The broker received a malformed frame, for example one with an incorrect frame type or a frame boundary that does not align with the expected structure. This is a hard error and the connection is closed.
- 502 syntax-error The broker received a frame containing a command or arguments that do not conform to the AMQP syntax. This is a hard error and the connection is closed.
- 503 command-invalid The client sent a command that is not valid in the current channel or connection state, such as sending a channel-level command before the channel is open. This is a hard error.
- 504 channel-error The client attempted a channel-level operation in a situation where it is not appropriate, such as re-opening a channel that has already been closed with a hard error. This is a hard error.
- 505 unexpected-frame The broker received a frame that is out of sequence for the current state of the channel or connection. This typically indicates a protocol implementation error on the client side.
- 506 resource-error The broker could not complete the operation because a required resource, such as memory or disk space, is exhausted. This is a hard error and the connection is closed.
- 530 not-allowed The client attempted an operation that is not permitted in the current context, for example trying to declare an exchange on a virtual host where it is forbidden. This is a hard error.
- 540 not-implemented The broker does not implement the requested method or a feature required to complete the operation. The client should not retry the same request.
- 541 internal-error An internal broker error occurred that prevented the operation from completing. This is a hard error; the connection is closed and the broker may log further details.