This topic provides solutions to common errors that occur when you connect a client to an ApsaraMQ for RocketMQ broker.
Why does the "signature validate by dauth failed" error occur during client connection?
Why does the "TimeoutException" error occur during client connection?
Why is the "valid resource owner failed" error returned by the client?
Why is the "MQClientException: No route info of this topic" error returned by the client?
Why is the "FETCH_TOPIC_ROUTE_FAILURE" error returned by the client?
Why is the "CODE: 25 DESC: the consumer's subscription not latest" error returned by the client?
Why does the "signature validate by dauth failed" error occur during client connection?
The AccessKey ID and AccessKey secret are incorrectly configured. Perform the following operations to troubleshoot the issue:
Check whether the copied AccessKey ID and AccessKey secret contain missing characters or extra spaces.
Check whether the obtained AccessKey ID and AccessKey secret belong to the same pair. For information about how to obtain an AccessKey pair, see Create an AccessKey pair.
Why does the "TimeoutException" error occur during client connection?
A network issue has occurred. Perform the following operations to troubleshoot the issue:
Run the telnet Endpoint domain name Port command to check the network connectivity.
If you are debugging an on-premises environment, check whether you are connected to the client by using a public endpoint.
Check whether you have enabled special network settings such as firewalls and jump servers.
Why is the "valid resource owner failed" error returned by the client?
Possible causes:
The endpoint or topic name is invalid. Make sure that the endpoint and topic name are correctly specified and that the topic is created on the instance that you want to access.
Permissions are not correctly granted. If you are a Resource Access Management (RAM) user, you must obtain the required permissions before you access ApsaraMQ for RocketMQ instances and the related resources.
For information about permission policies, see Policies and examples for ApsaraMQ for RocketMQ 5.0 instances or Policies and examples for ApsaraMQ for RocketMQ 4.0 instances.
Why is the "MQClientException: No route info of this topic" error returned by the client?
Possible causes:
The endpoint or topic name is invalid. Make sure that the endpoint and topic name are correctly specified and that the topic is created on the instance that you want to access.
Permissions are not correctly granted. If you are a Resource Access Management (RAM) user, you must obtain the required permissions before you access ApsaraMQ for RocketMQ instances and the related resources.
For information about permission policies, see Policies and examples for ApsaraMQ for RocketMQ 5.0 instances or Policies and examples for ApsaraMQ for RocketMQ 4.0 instances.
Why is the "FETCH_TOPIC_ROUTE_FAILURE" error returned by the client?
Possible causes:
The endpoint or topic name is invalid. Make sure that the endpoint and topic name are correctly specified and that the topic is created on the instance that you want to access.
Permissions are not correctly granted. If you are a Resource Access Management (RAM) user, you must obtain the required permissions before you access ApsaraMQ for RocketMQ instances and the related resources.
For information about permission policies, see Policies and examples for ApsaraMQ for RocketMQ 5.0 instances or Policies and examples for ApsaraMQ for RocketMQ 4.0 instances.
Why is the "CODE: 25 DESC: the consumer's subscription not latest" error returned by the client?
The broker reports its router information to a name server at a preset interval. If the network jitters and the latest subscription information cannot be pulled during this process, this warning appears when consumers consume messages.
Why is the "current message type not match with topic accept message types" error returned by the client?
ApsaraMQ for RocketMQ verifies the consistency between the message type of the topic and the type of messages that are received or delivered. Make sure that the message types are the same.
For example, if you want to receive and deliver ordered messages, the topic that you create must be used to receive or deliver ordered messages. Otherwise, the client returns the "current message type not match with topic accept message types" error.
The message type of a topic is specified when you create the topic.
The type of messages to be received and delivered is specified in the sample code of an SDK.