yuz10 opened a new issue, #8584:
URL: https://github.com/apache/rocketmq/issues/8584

   ### 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
   
   Ubuntu 24.04
   
   ### RocketMQ version
   
   5.3.0
   
   ### JDK Version
   
   1.8
   
   ### Describe the Bug
   
   issue #3905 adds brokerName in remoting protocol, but in sendMessageBack 
request, the brokerName is missing. 
   
   when request proxy, and the broker address is not available in network, the 
consumer cannot send message back.
   
   ### Steps to Reproduce
   
   start a consumer that returns RECONSUME_LATER
   
   ```
     DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("group");
   
           consumer.setNamesrvAddr("localhost:8080");
   
           consumer.subscribe("topic", "*");
           consumer.registerMessageListener(new MessageListenerConcurrently() {
   
               @Override
               public ConsumeConcurrentlyStatus consumeMessage(List<MessageExt> 
msgs, ConsumeConcurrentlyContext context) {
                   System.out.printf("%s Receive New Messages: %s %n", 
Thread.currentThread().getName(), msgs);
                   return ConsumeConcurrentlyStatus.RECONSUME_LATER;
               }
           });
   ```
   
   
   ### What Did You Expect to See?
   
   send message back request contains brokerName.
   
   ### What Did You See Instead?
   
   brokerName is null in send message back request. 
   
   ### 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