• Distributed Message Service

dms
  1. Help Center
  2. Distributed Message Service
  3. API Reference
  4. Appendix
  5. Error Code

Error Code

Table 1 DMS error codes

Status Code

Error Code

Description

400

10240002

The number of queried queues exceeds the upper limit.

400

10240005

The project ID format is invalid.

400

10240007

The name contains invalid characters.

400

10240009

The message body is not in JSON format or contains invalid characters.

400

10240010

The description contains invalid characters.

400

10240011

The name length must be 1 to 64 characters.

400

10240012

The name length must be 1 to 32 characters.

400

10240013

The description length must be 0 to 160 characters.

400

10240014

The number of consumable messages exceeds the maximum limit.

400

10240015

The queue ID format is invalid.

400

10240016

The group ID format is invalid.

400

10240017

The queue already exists.

400

10240018

The consumer group already exists.

400

10240019

The number of consumer groups exceeds the upper limit.

400

10240020

The quota is insufficient.

400

10240021

The value of time_wait is not within the value range of 1–60.

400

10240022

The value of max Consume Count must be within the range of 1–100.

400

10240027

The value of retention_hours must be an integer in the range of 1–72.

400

10240028

Non-kafka queue does not support retention_hours.

400

10240032

The queue is being created.

401

10240101

Invalid token.

401

10240102

Expired token.

401

10240103

Missing token.

401

10240104

Project ID does not match the token.

403

10240304

Change the quota of a queue or consumer group to a value smaller than the used quota.

403

10240306

The tenant has been frozen. You cannot perform operations on DMS.

403

10240308

The queue quota must be within the range of 1–20.

403

10240309

Access denied. You cannot perform operations on DMS.

403

10240310

The tenant is a read-only user and cannot perform operations on DMS.

403

10240311

The role is not assigned any permission and cannot perform operations on DMS.

403

10240312

The tenant is restricted and cannot perform operations on DMS.

404

10240401

The queue ID is incorrect or not found.

404

10240405

The consumption group ID is incorrect or not found.

404

10240406

The URL or endpoint does not exist.

500

10250002

An internal service error occurred.

500

10250003

An internal service error occurred.

500

10250004

An internal service error occurred.

500

10250005

The internal communication is abnormal.

500

10250006

An internal service error occurred.

400

10540001

The message body contains invalid fields.

400

10540003

Message ack status must be either 'success' or 'fail'. It should not be '{status}'.

400

10540004

Request error: The queue or group name does not match the handler.

400

10540010

The request format is incorrect: {error description}.

400

10540011

The message size is {message size}, larger than the size limit {max allowed size}.

400

10540012

The message body is not in JSON format or contains invalid characters.

400

10540014

The URL contains invalid parameters.

400

10540202

The request format is incorrect: {error description}.

400

10542204

Failed to consume messages due to {desc}.

400

10542205

Failed to obtain the consumption instance because the handler does not exist. This may be because the consumer instance is released 1 minute after the message is consumed. As a result, the consumer instance fails to be obtained from the handler.

This error code is returned in the following scenarios:

  • Submit the handler of another consumption instance after consumption.
  • The message consumption is acknowledged 1 minute after the message is consumed.
  • A dead letter message consumption API is used to acknowledge the consumption of normal messages.
  • A normal message consumption API is used to acknowledge the consumption of dead letter messages.

400

10542206

The value of ack_wait must be within the range of 15–300.

400

10542209

The handler does not exist because the handler fails to be parsed, the message consumption times out, or the message consumption is repeatedly acknowledged.

This error code is returned in the following scenarios:

  • A wrong handler is submitted after the message is consumed.
  • The message is not consumed and a fake handler is used to acknowledge the message consumption.
  • The message consumption is acknowledged 30s after the message is consumed.
  • A used handler is used to repeatedly acknowledge message consumption within 30s after the message is consumed.

Due to performance concerns, the system timeout timing mechanism is not very precise, and the system performs periodic timeout detection instead of real-time detection.

400

10542214

The request format is incorrect: {error description}.

404

10240407

The request is too frequent. Flow control is being performed. Please try again later.

404

10540401

The queue name does not exist.

400

10240035

The tag key is empty or too long.

400

10240036

The tag key contains invalid characters.

400

10240038

The tag value is too long.

400

10240039

The tag value contains invalid characters.

400

10240040

You can only create or delete tags.

400

10240041

You can only filter or count tags.

400

10240042

The number of records on each page for pagination query exceeds the upper limit.

400

10240043

The number of records on each page for pagination query exceeds the upper limit.

400

10240044

A maximum of 10 tags can be created.

400

10240045

The tag key has been used.

404

10240426

No tag containing this key exists.