Client Risk Explanation and Update Guide
Last updated: 2025-07-15 18:35:42
1. Java PushConsumer Sequential Messaging Cannot Guarantee Sequence in Specific Scenarios
Client List
Version 5.0.6 and lower versions may encounter this issue in some special scenarios. In cases of network exceptions, timeouts, etc., message order cannot be guaranteed. Related issue: [Bug] PushConsumer reentrant pop orderly doesn't work as expected.
Upgrading Client Operation Guide
Recommend upgrading to 5.0.7. Just direct upgrade the dependency version.
2. Golang Version Too Low, Route Table May Be Emptied
Client List
v5.0.1 and below may clear the route table when unable to obtain it due to network timeout in some scenarios. Related issue: golang: optimize the logic of obtaining routing tasks.
Upgrading Client Operation Guide
Recommend upgrading to v5.1.1-rc1. Just upgrade the dependency version directly.
3. Java Message Trace Possibly Incomplete
Client List
4.9.4 and below may encounter in some special scenarios.
Upgrading Client Operation Guide
Recommend upgrading to 4.9.5. Just direct upgrade the dependency version.
4. Go SDK First Launch May Display Error: fetch offset of mq from broker error
Client List
master branch and below may encounter, such as v2.1.2 and below, startup error
fetch offset of mq from broker error.Upgrading Client Operation Guide
We recommend upgrading to the latest master branch as the Commit ID version.
5. Java SDK Error Prompts during Consumption Process: the queue's messages, span too long, so do flow control
Client List
4.7.1 and below may encounter the above logs printed in logs during the consumption process, and the consumption will be rate-limited in some special scenarios.
Upgrading Client Operation Guide
Recommend upgrading to 4.9.5. Just direct upgrade the dependency version.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback