TDMQ for RocketMQ
- Release Notes and Announcements
- Announcements
- Product Introduction
- RocketMQ 5.x
- Introduction to RocketMQ 5.x
- Purchase Guide
- Getting Started
- Console Guide
- Cluster Management
- Message Query
- Permission Management
- Development Guide
- Message Type
- Consumption Mode
- SDK Documentation
- Practical Tutorial
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Billing Overview
- Getting Started
- Messaging over TCP
- Operation Guide
- Cluster Management
- Access Management (CAM)
- Tag Management
- Monitoring and Alarms
- Development Guide
- Message Types
- Practical Tutorial
- Access over HTTP
- SDK Documentation
- Access over TCP
- Spring Boot Starter
- SDK for Java
- Migration to Cloud
- Feeling Migration
- FAQs
Client Integration
Last updated: 2023-04-12 11:34:42
The error message “No route info of this topic” was prompted
Error details:
[org.apache.rocketmq.client.exception.MQClientException: No route info of this topic: generation%rocketmq-gab9bb2877z8|generation%video_task
General possible causes:Incorrect topic_name. Check whether the namespace is correct. The topic name shoud be formatted as
rocketmq-xxx|[ns]%[topicName].namespace refers to the name of a namespace, which can be copied under the Namespace tab on the cluster details page in the console.
topic_name refers to the name of a topic, which can be copied under the
Topic tab on the cluster details page in the console.Other possible causes:
Broker prohibits automatic creation of topics, and users do not manually create topics in the console.
Broker is not connected to Name Server correctly. Submit a ticket for assistance.
Producer is not connected to Name Server correctly. Check whether the access point is entered correctly.
The error message “Send [3] times, still failed, cost [334]ms” was prompted
Error details:
com.freesky.inspiration.domain.mq.MQProducerManager:sendMessage``[org.apache.rocketmq.client.exception.MQClientException: Send [3] times, still failed, cost [334]ms, Topic: video_task, BrokersSent: [broker-2, broker-0, broker-1]General possible causes:
No permissions. Check whether the namespace has been authorized.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No