RockteMQ-AI commented on issue #597: URL: https://github.com/apache/rocketmq-spring/issues/597#issuecomment-5431160875
**Issue Evaluation** Category: `bug` | Status: **Needs Info** This appears to be the same issue as #598 — the transaction message `checkLocalTransaction` callback keeps being triggered even after `executeLocalTransaction` returns `COMMIT`. A few observations: 1. RocketMQ Spring 2.2.x is designed for RocketMQ 4.x/5.x compatibility, but there may be behavioral differences in transaction state handling between broker versions. 2. If the message is consumed successfully but the check callback continues, this could indicate the transaction state is not being properly persisted on the broker side. Could you confirm: - [ ] Does this happen with both RocketMQ 5.1.4 and earlier versions? - [ ] Are you using the `TransactionalMessageProducer` or the annotation-based approach? - [ ] Can you share the broker logs for the transaction check requests? This will help determine if this is a version compatibility issue or a deeper transaction state management bug. --- *Automated evaluation by github-manager* -- 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]
