ApsaraMQ for RocketMQ:Troubleshooting

Issue

Suggestion

Unrecorded Logs Exist

The diagnostic system did not record certain logs. For assistance, submit a ticket.

Signature Algorithm Not Found

Check your Java Development Kit (JDK) and operating system versions, and check for dependency conflicts.

Consumption Exception

Check your consumer code. If the issue persists, submit a ticket.

Messages not consumed (console shows "Processing" but no client-side logs) — Add a log statement at the consumer entry point to print the message ID, confirming whether messages are reaching the client. If the console shows no delivery trace and the client has no logs, focus your investigation on the client-side receive layer.

Ordered messages stuck (manual ACK ineffective) — Ordered messages are processed sequentially within a queue. If one message is stuck, all subsequent messages in that queue are blocked. The server does not support manual ACK for ordered messages. Investigate your consumer-side business logic for excessive processing time or deadlocks.

Ordered consumption repeated pull — This typically occurs when the consumer fails to process a message (throws an exception or does not return ACK before timeout), triggering a client-side retry. Check your local client logs at /{user.home}/logs/rocketmq/rocketmq-client.log to confirm failure records, and investigate client-side performance issues (CPU, memory, full GC, and so on).

consumeTimeout parameter not taking effect — Verify that your SDK version supports the consumeTimeout parameter and that the configured value complies with the specification requirements.

Failed to Send Heartbeat

Verify that the topic and group resources exist. If this issue is accompanied by a network or backend service exception, follow the suggestions for those issues. If the issue persists, submit a ticket.

Failed to Acknowledge Consumption

If this issue is accompanied by a network or backend service exception, follow the suggestions for those issues. If the issue persists, submit a ticket.

Failed to Pull Message

Verify that the topic and group resources exist. If this issue is accompanied by a network or backend service exception, follow the suggestions for those issues. If the issue persists, submit a ticket.

Failed to Send Message

Verify that the topic resource exists. If this issue is accompanied by a network or backend service exception, follow the suggestions for those issues. If the issue persists, submit a ticket.

Frequent producer instance creation causing send failures — If the error contains checkCurrentState or a connection timeout, the likely cause is that your code (for example, inside a retry loop) calls buildProducer() to create a new instance on each invocation. A producer is a heavyweight object and must be maintained as a global singleton. Avoid repeatedly creating and destroying producer instances, and ensure your application has fully started before sending messages.

ONSClientException error — In addition to checking security group ports, the MQ allow-list, and telnet connectivity, verify that your code correctly sets the Namespace parameter: properties.setProperty(PropertyKeyConst.Namespace, "Instance ID");

Failed to Obtain Route Information

Verify that the topic resource exists. If this issue is accompanied by a network or backend service exception, follow the suggestions for those issues. If the issue persists, submit a ticket.

Failed to Disconnect Client

If this issue is accompanied by a network or backend service exception, follow the suggestions for those issues. You can ignore this error if it occurs when the application process terminates.

Throttling Triggered on Broker

Log on to the Message Queue for Apache RocketMQ console. On the instance dashboard, check the producer and consumer TPS and the number of throttled requests to determine if an instance upgrade is needed. For more information, see Upgrade or downgrade an instance.

Consumer Group Not Found

Verify that the group for the client subscription exists. Log on to the Message Queue for Apache RocketMQ console. On the Instances page, click the instance that the client accesses. On the Groups page, check if the group exists.

Invalid AccessKey ID

Verify that the authentication credentials in your client are correct.

• For 5.x instances:

  The instance username. You can obtain this on the Intelligent Authentication tab of the Access Control page in the Message Queue for Apache RocketMQ console.

• For 4.x instances:

  The AccessKey ID, which is the identifier for your Alibaba Cloud account. For more information, see Create an AccessKey pair.

Invalid AccessKey Secret

Verify that the authentication credentials in your client are correct.

• For 5.x instances:

  The instance password. You can obtain this on the Intelligent Authentication tab of the Access Control page in the Message Queue for Apache RocketMQ console.

• For 4.x instances:

  The AccessKey Secret, which is the key for your Alibaba Cloud account. For more information, see Create an AccessKey pair.

Invalid Scheduled Time for Scheduled Messages

Adjust the message delivery delay or upgrade your instance. For information about the supported delivery delay for each instance edition, see Quotas and limits.

Invalid Message Attribute

Review the error log and check for conflicting message properties. For more information, see Internal message properties.

Message Type Mismatch

Ensure that the message type configured for the topic in the console matches the message type your code sends.

Full Local Message Cache

This indicates that the message consumption rate is too low. Review your consumption logic.

Network Error

A network error occurred. For assistance, submit a ticket.

No Online Consumer Client

Log on to the Message Queue for Apache RocketMQ console. On the Instances page, click the instance that the client accesses. Then, on the Groups page, click the group ID used by the client.

• For 5.x instances:

  On the Group Details page, click the Running Information tab. In the Client Connection section, verify that the client is listed and check its consumption status.

• For 4.x instances:

  In the Client Connection Information section, verify that the client is listed and check its consumption status.

Messages not consumed (console shows "Processing" but no client-side logs) — Add a log statement at the consumer entry point to print the message ID, confirming whether messages are reaching the client. If the console shows no delivery trace and the client has no logs, focus your investigation on the client-side receive layer.

Ordered messages stuck (manual ACK ineffective) — Ordered messages are processed sequentially within a queue. If one message is stuck, all subsequent messages in that queue are blocked. The server does not support manual ACK for ordered messages. Investigate your consumer-side business logic for excessive processing time or deadlocks.

Ordered consumption repeated pull — This typically occurs when the consumer fails to process a message (throws an exception or does not return ACK before timeout), triggering a client-side retry. Check your local client logs at /{user.home}/logs/rocketmq/rocketmq-client.log to confirm failure records, and investigate client-side performance issues (CPU, memory, full GC, and so on).

consumeTimeout parameter not taking effect — Verify that your SDK version supports the consumeTimeout parameter and that the configured value complies with the specification requirements.

Local Request Missing

Possible causes:

1. The client is stuck due to an issue such as a full garbage collection (GC).

2. The client retransmitted the request due to a network issue. You can ignore occasional occurrences.

Backend Service Exception

A broker-side exception occurred. For assistance, submit a ticket.

Inconsistent Subscriptions

Log on to the Message Queue for Apache RocketMQ console. On the Instances page, click the instance that the client accesses. On the Groups page, click the group ID that the client uses. On the Group Details page, check the Subscriptions section for inconsistencies. Ensure all consumers in a group subscribe to the same topics. For more information, see Subscriptions.

Subscription Does Not Exist

Check whether the consumer client is online and the network is functioning correctly.

Topic Not Found

Verify that the topic your client uses exists. Log on to the Message Queue for Apache RocketMQ console. On the Instances page, click the instance that the client accesses. On the Topics page, check if the topic exists.

Request Code Not Supported

A common example is error code 320, which indicates that batch messaging is not supported.

Check item

Issue

Suggestion

Instance

Instance Does Not Exist

Check the instance name.

Instance Not Running

Check the instance status.

Topic

Topic Does Not Exist

Check if the topic was created in the console.

Broker

Machine Failure

A machine in the backend broker cluster has failed. This may cause a temporary network error, which you can ignore.

Broker Update Released

The backend broker cluster is undergoing maintenance, which might cause a brief network disruption and temporary errors in client logs. You can ignore these errors. If you did not receive a maintenance notification, submit a ticket.