**It's wired.**
When I changed the logger of `RocketmqClient` to `slf4j`, and changed the
`level` to `WARN`,
like `<logger name="RocketmqClient" level="WARN"/>`, Everything became chaos.
If the `level` is `INFO`, everything will be OK.
I don't know why, but I guess the issue may be concurrent problem.
When `INFO` log was disabled, possibly some thread run faster, likely 1ms,
which make this happen:
```
if (subscriptionData.getSubVersion() < requestHeader.getSubVersion()) {
log.warn("The broker's subscription is not latest, group: {} {}",
requestHeader.getConsumerGroup(),
subscriptionData.getSubString());
response.setCode(ResponseCode.SUBSCRIPTION_NOT_LATEST);
response.setRemark("the consumer's subscription not latest");
return response;
}
```
**RocketMQ version: 4.3.1**
[ Full content available at: https://github.com/apache/rocketmq/issues/363 ]
This message was relayed via gitbox.apache.org for [email protected]
