RockteMQ-AI commented on issue #11375: URL: https://github.com/apache/rocketmq/issues/11375#issuecomment-6123019728
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified based on the detailed analysis provided. **Root Cause:** `ReceiptHandle.decode` throws `IllegalArgumentException` for malformed handles, which is not caught in the gRPC v2 consumer path and falls through to the generic `INTERNAL_SERVER_ERROR` handler in `ResponseBuilder#buildStatus(Throwable)`. This bypasses the proper `INVALID_RECEIPT_HANDLE` mapping that exists for expired handles. **Impact:** - Official clients (`rocketmq-clients` `ProcessQueueImpl#ackMessage`) retry ack indefinitely for `INTERNAL_SERVER_ERROR`, creating endless retry loops - Batch operations fail entirely when one entry has a malformed handle - Server logs show misleading `internal server error` instead of actionable client error **Severity:** High — affects message consumption reliability and causes alert noise **Affected Components:** - `AckMessageActivity#processAckMessage` - `AckMessageActivity#ackMessageInBatch` - `ChangeInvisibleDurationActivity` - `ForwardMessageToDeadLetterQueue` - gRPC v2 consumer path in Proxy **Suggested Fix:** Catch `IllegalArgumentException` from `ReceiptHandle.decode` and map it to `ProxyException(ProxyExceptionCode.INVALID_RECEIPT_HANDLE)` or return `Code.INVALID_ARGUMENT` as documented in `service.proto`. An automated fix proposal will be generated. Reply `/approve` 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]
