Client Risk Descriptions and Update Guide
Last updated:2026-01-23 17:36:45
1. Order Not Guaranteed for Ordered Messages Consumed by Java PushConsumer in Specific Scenarios
Client List
Versions 5.0.6 and earlier may encounter this issue in special scenarios. In scenarios such as network exceptions or timeouts, message order cannot be guaranteed. Related issue: [Bug] PushConsumer reentrant pop orderly doesn't work as expected.
Client Upgrade Operation Guide
It is recommended to upgrade the dependency version to 5.0.7.
2. Low Golang Version May Cause the Route Table to Be Cleared
Client List
In versions 5.0.1 and earlier, the route table may be cleared when it cannot be obtained due to network timeouts. Related issue: golang: optimize the logic of obtaining routing tasks.
Client Upgrade Operation Guide
It is recommended to upgrade the dependency version to v5.1.1-rc1.
3. Java Message Traces May Be Incomplete
Client List
Versions 4.9.4 and earlier may encounter this issue in special scenarios.
Client Upgrade Operation Guide
It is recommended to upgrade the dependency version to 4.9.5.
4. The Error "fetch offset of mq from broker error" May Occur When the Go SDK Starts for the First Time
Client List
This issue may occur in versions under the master branch, such as v2.1.2 and earlier, resulting in the startup error:
fetch offset of mq from broker error.Client Upgrade Operation Guide
It is recommended to upgrade to the latest master branch as the commit ID version.
5. The Error "the queue's messages, span too long, so do flow control" Occur in the Java SDK Consumption Process
Client List
Versions 4.7.1 and earlier may encounter this issue in special scenarios. During message consumption, logs may print entries such as the above, and consumption will be throttled.
Client Upgrade Operation Guide
It is recommended to upgrade the dependency version to 4.9.5.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback