The client log file of Message Queue for Apache RocketMQ is ons.log, which includes INFO, WARN, and ERROR logs.

This topic describes common client log information, helping you obtain information from the printed logs and determine the current status to troubleshoot faults.

The following table lists log information in the ons.log file (continuously updated).

Log level Printed 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 indicates that the message has been consumed and the consumption progress has been made persistent on the Message Queue for Apache RocketMQ broker. MessageQueue includes the message topic, corresponding broker name, and consumption queue ID. N/A
INFO [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 printed information displays the transactions per second (TPS) when messages are pulled by calling consumeQueue. N/A
WARN [TIMEOUT_CLEAN_QUEUE]broker busy, start flow control for a while, period in queue: 905ms, size of queue: 1164 The Message Queue for Apache RocketMQ broker is under high pressure and cannot process so many requests. The broker writes data into pageCache first and then flushes the disk when storing data. Therefore, the expired requests are cleared every 10 seconds (this process can determine whether the cache page is busy).
  1. Add brokers to share the pressure.
  2. Increase the value of osPageCacheBusyTimeOutMills.
WARN 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 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 need to consume messages. N/A
WARN [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, an attempt is made to lock the message queue. If the message queue is not locked within one second, the current message queue is being accessed by other consumers and cannot be unlocked. N/A
WARN doRebalance, XXX-CID, add a new mq failed, MessageQueue [topic=XXXX, brokerName=szorder2-XX, queueId=X], because lock failed An ordered topic is used currently. To ensure the ordered consumption of messages in a single shard, a lock mechanism is enabled. If this log is printed for a client, consumers have started to consume messages in a shard. N/A
WARN 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 pair is incorrect. An AccessKey pair consists of an AccessKey ID and an AccessKey secret.
  • No group ID is created under the current instance in the console.
  • In the instantiation code, NameServerAddr is incorrect.
  • Configure the AccessKey pair correctly.
  • Create a group ID under the current instance.
  • We recommend that you configure NameServerAddr for Java SDK 1.8.0 or later versions. The parameter can be obtained from the Message Queue for Apache RocketMQ console, which is inconsistent with the ONSAddr configured in earlier versions.
WARN com.aliyun.openservices.ons.api.impl.authority.exception.AuthenticationException: signature validate by dauth failed The AccessKey pair is incorrect. An AccessKey pair consists of an AccessKey ID and an AccessKey secret. Configure the AccessKey pair for creating the group ID.
WARN 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 is not pushed to the Message Queue for Apache RocketMQ broker. Add the group ID information to the subscription.json file.
WARN 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. N/A