RockteMQ-AI commented on issue #11172: URL: https://github.com/apache/rocketmq/issues/11172#issuecomment-5700656213
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** When `asyncSendEnable=true`, both the single-message and batch send paths in `SendMessageProcessor` attach only `thenAcceptAsync(...)` to the store future. If `asyncPutMessage(...)` / `asyncPutMessages(...)` completes exceptionally, the consumer is never invoked, and since the processor already returned `null`, no `doResponse(...)` path remains — the client hangs until remoting timeout. **Impact:** Broker → client communication gap on store write failures. Clients experience silent timeouts instead of receiving a `SYSTEM_ERROR` response. The after-send hook is also skipped. **Severity:** High — affects message send reliability under store failure conditions. **Suggested Fix:** Add `.exceptionally(...)` or `.whenComplete(...)` to both the single-message and batch async paths to handle exceptional completion by sending a `SYSTEM_ERROR` response and executing the after-send hook. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *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]
