dxt1218 opened a new issue, #673:
URL: https://github.com/apache/rocketmq-spring/issues/673

   The issue tracker is **ONLY** used for bug report and feature request. 
   
   Any question or RocketMQ proposal please use our [mailing 
lists](http://rocketmq.apache.org/about/contact/).
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
   我项目在从 rocketmq-spring:2.1.1 升级到 rocketmq-spring:2.3.0的过程 
   - What did you expect to see?
   发现一些项目消费者启动失败
   Caused by: org.apache.rocketmq.client.exception.MQClientException: 
consumeThreadMin (20) is larger than consumeThreadMax (1)
   
![image](https://github.com/user-attachments/assets/e4f0ab2b-bea7-4b8d-87f2-6dc131a942c0)
   
![image](https://github.com/user-attachments/assets/ec574386-830f-4b87-84c6-a341c9b1eecb)
   
![image](https://github.com/user-attachments/assets/4be25926-66fd-48f3-8fa2-6b4d445edbe9)
   
    **rocketmq-spring:2.1.1项目中的代码是有做兜底的**
   
![image](https://github.com/user-attachments/assets/efb9f1fc-9398-4db8-849a-9d32ce63e6b4)
   
   - What did you see instead?
   项目正常的启动
   2. Please tell us about your environment:
    rocketmq-spring:2.3.0    jdk8     rocketmq-clinet:5.2.0 
   3. Other information (e.g. detailed explanation, logs, related issues, 
suggestions how to fix, etc):
   
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   以往可以平滑兼容低版本的代码,不然我需要将项目上的注解都要做 consumeThreadNumber字段的声明,
   或者代码上将    int consumeThreadNumber() default 1; 默认值为1也好。
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   3. Indicate the importance of this issue to you (blocker, must-have, 
should-have, nice-to-have). Are you currently using any workarounds to address 
this issue?
   


-- 
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