yyello206-netizen opened a new issue, #10556:
URL: https://github.com/apache/rocketmq/issues/10556

   ### 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
   
   ubantu 20.04 Runtime platform environment: DOCKER
   
   ### RocketMQ version
   
   5.3.1
   
   ### JDK Version
   
   1.8
   
   ### Describe the Bug
   
   @Override
           protected SubscriptionGroupConfig getDirectly(String consumerGroup) 
throws Exception {
               ProxyConfig config = ConfigurationManager.getProxyConfig();
               String clusterName = config.getRocketMQClusterName();
               Optional<BrokerData> brokerDataOptional = 
findOneBroker(clusterName);
               if (brokerDataOptional.isPresent()) {
                   String brokerAddress = 
brokerDataOptional.get().selectBrokerAddr();
                   return 
mqClientAPIFactory.getClient().getSubscriptionGroupConfig(brokerAddress, 
consumerGroup, DEFAULT_TIMEOUT);
               }
               return EMPTY_SUBSCRIPTION_GROUP_CONFIG;
           }
   
   ### Steps to Reproduce
   
   启动后proxy会报no topic route from namesrv
   
   ### What Did You Expect to See?
   
   解决这个bug,发布新版本
   
   ### What Did You See Instead?
   
   很紧急
   
   ### 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