majialoong opened a new issue, #10620: URL: https://github.com/apache/rocketmq/issues/10620
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment All ### RocketMQ version 5.x ### JDK Version All ### Describe the Bug In Local Proxy mode, `LocalRemotingCommand` does not initialize `processTimer` because the request does not pass through `NettyDecoder`. This causes a `NullPointerException` in the `ChannelFutureListener` of `NettyRemotingAbstract.writeResponse` when recording the RPC latency. ### Steps to Reproduce 1. Start RocketMQ Proxy in Local mode. 2. Send a message through the gRPC endpoint. 3. Inspect `NettyRemotingAbstract.writeResponse` when the response is written. 4. Observe that `request.getProcessTimer()` is `null`. <img width="752" height="407" alt="Image" src="https://github.com/user-attachments/assets/2a88fcc6-9196-4a7a-af3f-1cb6c537f54b"; /> ### What Did You Expect to See? The local request should have an initialized process timer, and the RPC latency metric should be recorded successfully. ### What Did You See Instead? A `NullPointerException` occurs when calling `request.getProcessTimer().elapsed(...)`. ### Additional Context _No response_ -- 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]
