RockteMQ-AI commented on issue #716: URL: https://github.com/apache/rocketmq-spring/issues/716#issuecomment-5310371949
**Issue Evaluation** Category: `bug` | Status: **Needs Verification** The report indicates that setting `RocketMQHeaders.TAGS` via `MessageBuilder.setHeader()` does not survive the message conversion in `RocketMQUtil.toRocketMQMessage()` — the TAGS header is silently dropped. Looking at the referenced code path (`RocketMQUtil.java` line 211), the conversion iterates over message headers but may not handle `RocketMQHeaders.TAGS` (which maps to the system-level `tags` property) the same way it handles `KEYS` or other user properties. If TAGS is consumed to set `MessageExt.tags` but not preserved in the user-property map, downstream consumers that read tags from headers would see them as missing. To help verify and fix this, could you provide: - [ ] The RocketMQ Spring version where this occurs - [ ] A minimal reproducer showing the sent message vs. what the consumer receives - [ ] Whether the tag is visible on the broker side (e.g. via `mqadmin consumerProgress` or dashboard) This will help determine whether the fix belongs in the send-side conversion (`toRocketMQMessage`) or the receive-side header reconstruction. --- *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]
