Aias00 opened a new issue, #10730:
URL: https://github.com/apache/rocketmq/issues/10730
## Problem
`LocalMessageService.popMessage` logs a full `MessageExt` when POP offset
metadata is inconsistent:
```java
log.warn("Queue offset [{}] of msg is strange, not equal to the stored in
msg, {}", msgQueueOffset, messageExt);
```
`MessageExt.toString()` delegates to `Message.toString()`, which prints
`Arrays.toString(body)`. This warning can expose message payload bytes in proxy
logs.
## Scope
Track 2 / Proxy runtime diagnostics hardening. This should only change log
content, not POP offset handling behavior.
## Expected behavior
- Do not log raw `MessageExt` in `LocalMessageService`.
- Keep useful diagnostics such as topic, msgId, queueId, queueOffset, body
size, and property keys.
- Add targeted test coverage for the summary helper.
## Evidence
-
`proxy/src/main/java/org/apache/rocketmq/proxy/service/message/LocalMessageService.java`
logs `messageExt` directly.
-
`common/src/main/java/org/apache/rocketmq/common/message/Message.java#toString`
includes `Arrays.toString(body)`.
--
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]
