Logs

Log level

Printing information

Description

Solution

INFO

[persistAll] Group: CID_XXXX ClientId: 10.31.40.100@171374#14159XXX#-2036649XXX#20931314294957XXX updateConsumeOffsetToBroker MessageQueue [topic=XXXX, brokerName=qdinternetorder-XX, queueId=X] 1013XXX

This message indicates that a message was consumed successfully and the consumption progress was persisted on the Message Queue server-side. The MessageQueue object contains the message topic, the corresponding brokerName, and the ID of the consumption queue.

Not applicable

[PULL_TPS] [CID_XXXX@CID_XXXX] Stats In One Minute, SUM: 0 TPS: 0.00 AVGPT: 0.00</br>[PULL_RT] [%RETRY%CID_XXXX@CID_XXXX] Stats In One Minute, SUM: 0 TPS: 0.00 AVGPT: 0.00

This message shows the Transaction Per Second (TPS) when messages are pulled from the consumeQueue.

Not applicable

WARN

[TIMEOUT_CLEAN_QUEUE]broker busy, start flow control for a while, period in queue: 905ms, size of queue: 1164

The Message Queue server-side is under high pressure and cannot process an excessive number of requests. The server-side first writes data to the pageCache and then flushes it to the disk. Therefore, it clears expired requests every 10 seconds. During this process, it checks if the page cache is busy.

1. Scale out and add more brokers to distribute the pressure.

2. Increase the value of the osPageCacheBusyTimeOutMills property.

execute the pull request exceptioncom.aliyun.openservices.shade.com.alibaba.rocketmq.client.exception.MQBrokerException: CODE: 25 DESC: the consumer's subscription not latest

The broker reports its routing information to the NameServer at regular intervals. If network jitter occurs, the client cannot pull the latest subscription information. This causes the warning to appear when the consumer consumes messages.

Not applicable

[WRONG]mq is consuming, so can not unlock it, MessageQueue [topic=XX, brokerName=szorder2-02, queueId=1]. maybe hanged for a while, 2

During load balancing, the system attempts to lock the message processing queue. If the lock is not acquired within 1 second, it indicates that a consumer is already accessing the queue and the queue cannot be unlocked.

Not applicable

doRebalance, XXX-CID, add a new mq failed, MessageQueue [topic=XXXX, brokerName=szorder2-XX, queueId=X], because lock failed

This occurs when you use an ordered topic. A locking mechanism ensures the ordered consumption of messages in a single partition. This client log message indicates that another client is already consuming messages from one of the partitions.

Not applicable

get Topic [XXXXXX] RouteInfoFromNameServer is not exist valuecom.aliyun.openservices.shade.com.alibaba.rocketmq.client.exception.MQClientException: CODE: 17 DESC: No topic route info in name server for the topic: TOPIC_XXXXX</br>See http://rocketmq.apache.org/docs/faq/ for further details.

• The AccessKey, which includes the AccessKey ID and AccessKey secret, is configured incorrectly.

• The Group ID (GID) was not created for the current instance in the console.

• The NameServerAddr parameter is not configured correctly in the instantiation code.

• Configure the correct AccessKey.

• Create a GID for the current instance in the console.

• For Java SDK 1.8.0 and later, configure the NameServerAddr parameter. You can obtain this parameter from the Message Queue console. This parameter is different from the ONSAddr parameter that is configured in earlier versions.

com.aliyun.openservices.ons.api.impl.authority.exception.AuthenticationException: signature validate by dauth failed

The AccessKey, which includes the AccessKey ID and AccessKey secret, is configured incorrectly.

Configure the AccessKey that was used to create the GID.

NettyClientPublicExecutor_3 - execute the pull request exceptioncom.aliyun.openservices.shade.com.alibaba.rocketmq.client.exception.MQBrokerException: CODE: 26 DESC: subscription group [CID_XXX] does not exist, See http://rocketmq.apache.org/docs/faq/ for further details.

The subscription relationship was not pushed to the Message Queue broker.

Add the GID information directly to the subscription.json file.

execute the pull request exceptioncom.aliyun.openservices.shade.com.alibaba.rocketmq.client.exception.MQBrokerException: CODE: 24 DESC: the consumer's subscription not exist

The subscription relationship is missing.

Not applicable

Can not find name server with endpoint

This usually occurs because the instanceId and endpoint parameters are set incorrectly.

Configure the correct instanceId and endpoint.

ERROR

No route info of this topic,TP_XXXXX

This usually occurs because the client is connected to the wrong NameServer.

Log on to the NameServer machine. Run the netstat -an|grep 9876 command to check if the client is connected to the correct NameServer. Then, configure the correct NameServer.