RockteMQ-AI commented on issue #11373: URL: https://github.com/apache/rocketmq/issues/11373#issuecomment-6123030455
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified based on the detailed analysis provided. **Root Cause:** The remoting activities (`AckMessageActivity`, `ChangeInvisibleDurationActivity`, `PopMessageActivity`) are instantiated with specific `RemotingCommand` request codes, but the corresponding processors are registered for different request codes in `RemotingProtocolProcessor#registerProcessors`. This mismatch causes requests to be routed to the wrong processors or no processor at all. **Impact:** - POP requests fail with `REQUEST_CODE_NOT_SUPPORT` - ACK requests receive no response (silently dropped) - CHANGE_MESSAGE_INVISIBLETIME requests receive no response - Message consumption and visibility timeout management completely broken in remoting v1 path **Severity:** Critical — core message consumption functionality is non-functional **Affected Components:** - `AckMessageActivity` (registered for `UPDATE_CONSUMER_OFFSET` but instantiated with `ACK_MESSAGE`) - `ChangeInvisibleDurationActivity` (registered for `UPDATE_CONSUMER_OFFSET` but instantiated with `CHANGE_MESSAGE_INVISIBLE_TIME`) - `PopMessageActivity` (registered for `POP_MESSAGE` but instantiated with different code) - `RemotingProtocolProcessor#registerProcessors` **Suggested Fix:** Align the request codes used in activity instantiation with the request codes used in processor registration. Either: 1. Change activity instantiation to use the correct request codes that match processor registration, or 2. Change processor registration to match the request codes used in activity instantiation 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]
