RockteMQ-AI commented on issue #10786: URL: https://github.com/apache/rocketmq/issues/10786#issuecomment-5163820413
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase (`develop@eddb235c1bd8`). **Root Cause:** `LocalMessageService.popMessage(...)` dereferences `sortMap.get(key)`, `msgOffsetInfo.get(key)`, and `startOffsetInfo.get(key)` without null checks or bounds validation. When broker POP response metadata is incomplete or inconsistent, this can throw `NullPointerException` or `IndexOutOfBoundsException`. **Impact:** Local-mode POP requests fail entirely when any offset metadata is malformed, instead of skipping the bad entry and continuing. **Severity:** medium — requires inconsistent broker metadata to trigger. **File:** `proxy/src/main/java/org/apache/rocketmq/proxy/service/message/LocalMessageService.java` (lines 288-295) An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager-bot* -- 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]
