RockteMQ-AI commented on issue #719: URL: https://github.com/apache/rocketmq-spring/issues/719#issuecomment-5473199729
**Issue Evaluation** Category: `bug` | Status: **Needs Investigation** Thank you for reporting this. The issue you describe — message trace showing "not consumed" in Alibaba Cloud RocketMQ 5.0 console while actual consumption works correctly — is likely a compatibility issue between `rocketmq-spring-boot-starter 2.3.3` and the RocketMQ 5.0 server's message trace feature. **Possible causes:** 1. The trace data format may have changed in RocketMQ 5.0, and the 2.3.3 client may not be sending trace data in the expected format 2. The trace topic (`RMQ_SYS_TRACE_TOPIC`) configuration may differ between 4.x and 5.0 **Suggested actions:** - Verify that `enableMsgTrace=true` is set in your consumer configuration - Check if upgrading to a newer version of `rocketmq-spring-boot-starter` (if available) resolves the trace compatibility - As a workaround, you can check consumption status via the broker's consumer group lag metrics instead of the trace UI This requires further investigation against the RocketMQ 5.0 trace protocol. Maintainers: please confirm if there is a known compatibility issue between spring-boot-starter 2.3.3 and RocketMQ 5.0 trace. --- *Automated evaluation by RockteMQ-AI* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
