drpmma commented on issue #653:
URL:
https://github.com/apache/rocketmq-spring/issues/653#issuecomment-2128790285
可以将你的代码示例贴出来吗，这样别人碰到相同的问题看到你的issue也就可以解决了；
另外，group确实不应当和应用一对一绑定，可以是一个多对一的关系，从最佳实践来看，变更订阅关系的时候也是建议新建group来启用新的订阅关系
Can you post your code example? This way, others faci
hachikozjq commented on issue #653:
URL:
https://github.com/apache/rocketmq-spring/issues/653#issuecomment-2128665189
>
在rocketmq中，可以通过consumer多次调用subscribe，使得一个consumer能够同时订阅多个topic；阅读了一下rocketmq-spring的代码，org.apache.rocketmq.spring.support.DefaultRocketMQListenerContainer，看起来是不支持这种做法的。
hachikozjq closed issue #653: 一个应用只允许一个gid，但是有好几个消费类（不同业务不同的topic），导致订阅关系不一致
URL: https://github.com/apache/rocketmq-spring/issues/653
--
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 com
drpmma commented on issue #653:
URL:
https://github.com/apache/rocketmq-spring/issues/653#issuecomment-2126178232
在rocketmq中，可以通过consumer多次调用subscribe，使得一个consumer能够同时订阅多个topic；阅读了一下rocketmq-spring的代码，org.apache.rocketmq.spring.support.DefaultRocketMQListenerContainer，看起来是不支持这种做法的。
I
drpmma commented on issue #653:
URL:
https://github.com/apache/rocketmq-spring/issues/653#issuecomment-2126169393
最简单的解决方案，不要让gid和应用绑定，gid本身就是一个消费组集群的概念，和应用不应该绑定。
The simplest solution is not to bind the gid with the application, as the
gid itself represents the concept of a consumer
hachikozjq opened a new issue, #653:
URL: https://github.com/apache/rocketmq-spring/issues/653
如题，有没有好的解决方案？
@RocketMQMessageListener(
topic = "topic1",
consumerGroup = "spring-application-name",
messageModel = MessageModel.CLUSTERING
)
public class A
