RockteMQ-AI commented on issue #2659: URL: https://github.com/apache/rocketmq-dashboard/issues/2659#issuecomment-5449101364
**Issue Evaluation** Category: | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In (line ~507-511), the batch deletion loop only catches . However, internally calls and for APACHE-type instances, which can throw unchecked runtime exceptions (e.g., ) when the broker or local dependency is unavailable. These uncaught exceptions propagate out of the loop, aborting the entire batch operation. **Relevant code** (): **Impact:** When one instance triggers a non- failure, all subsequent instances in the batch are skipped, and the endpoint returns a generic 500 instead of partial batch results. **Severity:** Medium — affects batch operation reliability; data loss risk is low since deletions are guarded, but operational UX degrades significantly. **Suggested fix:** Broaden the catch clause to also handle (or add a second catch block), recording the failure per-instance so the remaining instances are still attempted. An automated fix proposal can be generated. Reply to proceed with PR generation. --- *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]
