You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue tracker is ONLY used for bug report and feature request.
Any question or RocketMQ proposal please use our mailing lists.
BUG REPORT
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)
rocketmq-spring:2.1.1项目中的代码是有做兜底的
What did you see instead?
项目正常的启动
Please tell us about your environment:
rocketmq-spring:2.3.0 jdk8 rocketmq-clinet:5.2.0
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
FEATURE REQUEST
Please describe the feature you are requesting.
以往可以平滑兼容低版本的代码,不然我需要将项目上的注解都要做 consumeThreadNumber字段的声明,
或者代码上将 int consumeThreadNumber() default 1; 默认值为1也好。
Provide any additional detail on your proposed use case for this feature.
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?
The text was updated successfully, but these errors were encountered:
The issue tracker is ONLY used for bug report and feature request.
Any question or RocketMQ proposal please use our mailing lists.
BUG REPORT
我项目在从 rocketmq-spring:2.1.1 升级到 rocketmq-spring:2.3.0的过程
发现一些项目消费者启动失败
Caused by: org.apache.rocketmq.client.exception.MQClientException: consumeThreadMin (20) is larger than consumeThreadMax (1)
rocketmq-spring:2.1.1项目中的代码是有做兜底的
项目正常的启动
rocketmq-spring:2.3.0 jdk8 rocketmq-clinet:5.2.0
FEATURE REQUEST
Please describe the feature you are requesting.
以往可以平滑兼容低版本的代码,不然我需要将项目上的注解都要做 consumeThreadNumber字段的声明,
或者代码上将 int consumeThreadNumber() default 1; 默认值为1也好。
Provide any additional detail on your proposed use case for this feature.
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?
The text was updated successfully, but these errors were encountered: