Focus-rth opened a new issue, #7890:
URL: https://github.com/apache/rocketmq/issues/7890

   ### 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
   
   linux
   
   ### RocketMQ version
   
   develop
   
   ### JDK Version
   
   jdk 11
   
   ### Describe the Bug
   
   PullMessageProcessor
   
![image](https://github.com/apache/rocketmq/assets/4122322/20f48d0b-aaf4-4df1-ba8c-730cd6eb708c)
   
   NettyRemotingAbstract
   
![image](https://github.com/apache/rocketmq/assets/4122322/01cdaa50-058b-43a9-a3c5-9b558fcb34bc)
   
![image](https://github.com/apache/rocketmq/assets/4122322/6347361a-9b10-481d-a90c-5811b7927d04)
   
   uses asynchronous return, causing the Response in doAfterResponse of 
NettyRemotingAbstract rpcHook to be null
   
   
   ### Steps to Reproduce
   
   After successfully pulling the message asynchronously, watch the 
doAfterResponse of rpcHook
   
   ### What Did You Expect to See?
   
   After successfully pulling the message asynchronously, the doAfterResponse 
of rpcHook is call correct
   
   ### What Did You See Instead?
   
   uses asynchronous return,  the Response in doAfterResponse of 
NettyRemotingAbstract rpcHook to be null
   
   
   ### 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]

Reply via email to