This topic describes common errors that occur when a client connects to an ApsaraMQ for RocketMQ server and helps you quickly resolve the issues.
The "signature validate by dauth failed" error occurs during client connection
The "TimeoutException" error occurs during client connection
The client returns the "MQClientException: No route info of this topic" error
The client returns the "CODE: 25 DESC: the consumer's subscription not latest" error
The client returns the "current message type not match with topic accept message types" error
The "signature validate by dauth failed" error occurs during client connection
This error occurs if the AccessKey and SecretKey are configured incorrectly. The possible causes are as follows:
The copied AccessKey or SecretKey is missing characters or contains extra spaces.
The AccessKey and SecretKey do not match. For more information about how to obtain an AccessKey pair, see Create an AccessKey.
The "TimeoutException" error occurs during client connection
This error indicates a network issue. The possible causes are as follows:
You can run the telnet <endpoint domain name> <port> command to check network connectivity.
If you are in a local debugging environment, check whether you are using a public endpoint to access the server-side.
You can check for special network settings, such as firewalls or jump servers.
The client returns the "valid resource owner failed" error
Possible causes:
The endpoint or topic name is incorrect. Make sure that the endpoint and topic name are spelled correctly. Also, make sure the topic is created in the instance that you want to access.
The Resource Access Management (RAM) user does not have the required permissions. You must grant permissions to the RAM user before the user can access ApsaraMQ for RocketMQ instances and related resources.
For more information about access policies, see Authorization policies for Version 5.0 instances or Authorization policies for Version 4.0 instances.
The client returns the "MQClientException: No route info of this topic" error
Possible causes:
The endpoint or topic name is incorrect. Make sure that the endpoint and topic name are spelled correctly. Also, make sure the topic is created in the instance that you want to access.
The Resource Access Management (RAM) user does not have the required permissions. You must grant permissions to the RAM user before the user can access ApsaraMQ for RocketMQ instances and related resources.
For more information about access policies, see Authorization policies for Version 5.0 instances or Authorization policies for Version 4.0 instances.
For more information, see How do I troubleshoot the "No route info" error that occurs when I use an SDK to connect to ApsaraMQ for RocketMQ?
The client returns the "FETCH_TOPIC_ROUTE_FAILURE" error
Possible causes:
The endpoint or topic name is incorrect. Make sure that the endpoint and topic name are spelled correctly. Also, make sure the topic is created in the instance that you want to access.
The Resource Access Management (RAM) user does not have the required permissions. You must grant permissions to the RAM user before the user can access ApsaraMQ for RocketMQ instances and related resources.
For more information about access policies, see Authorization policies for Version 5.0 instances or Authorization policies for Version 4.0 instances.
The client returns the "CODE: 25 DESC: the consumer's subscription not latest" error
A broker reports its routing information to a name server at specified intervals. This warning is returned when a consumer consumes messages if network jitter prevents the client from retrieving the latest subscription information.
The client returns the "current message type not match with topic accept message types" error
ApsaraMQ for RocketMQ validates that the topic type and the message type are consistent. Make sure that the topic type is the same as the type of the messages that you send.
For example, if you send and receive ordered messages, the topic that you create must also be of the ordered message type. Otherwise, the client returns a mismatch error.
The topic type is selected when you create the topic.
The message type is specified in the code of the SDK that you use.