lizhanhui commented on issue #343: After deleting mqAdminExt 
subscriptionGroup,Again Automatically creating same Group
URL: https://github.com/apache/rocketmq/issues/343#issuecomment-412029443
 
 
   From your provided log, the __" auto create a subscription group, "__ is 
executed by PullMessageThread, aka, PullMessageProcesssor. 
PullMessageProcessor.java line #106 indeed examines existence of the mentioned 
subscription group through findSubscriptionGroupConfig(group) as below:
   ```java
       public SubscriptionGroupConfig findSubscriptionGroupConfig(final String 
group) {
           SubscriptionGroupConfig subscriptionGroupConfig = 
this.subscriptionGroupTable.get(group);
           if (null == subscriptionGroupConfig) {
               if 
(brokerController.getBrokerConfig().isAutoCreateSubscriptionGroup() || 
MixAll.isSysConsumerGroup(group)) {
                   subscriptionGroupConfig = new SubscriptionGroupConfig();
                   subscriptionGroupConfig.setGroupName(group);
                   SubscriptionGroupConfig preConfig = 
this.subscriptionGroupTable.putIfAbsent(group, subscriptionGroupConfig);
                   if (null == preConfig) {
                       log.info("auto create a subscription group, {}", 
subscriptionGroupConfig.toString());
                   }
                   this.dataVersion.nextVersion();
                   this.persist();
               }
           }
   
           return subscriptionGroupConfig;
       }
   ```
   This is the only method that may output such log. Apparently, it should not 
run into branch of creating new subscription and the follow-up log output 
confirms this: __The consumer's group info not exist, __.
   
   I am wondering if the conversion tool, IKVM, made some errors such as 
reorder the log statement out of the if-guard.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to