fluyu opened a new issue #322:
URL: https://github.com/apache/rocketmq-client-cpp/issues/322
**BUG REPORT**
1. Please describe the issue you observed:
- What did you do (The steps to reproduce)?
1. Start consuming using orderly PusherConsumer.
2. Send one message.
3. Hold the message inside the consume callback(ie. not returning the
callback)
- What did you expect to see?
The message should not been commited to the broker and the consumer
group should have 1 message delay
- What did you see instead?
From the console, found the consum offset been updated to the latest, no
delay
2. Please tell us about your environment:
- What is your OS?
> CentOS 7
- What is your client version?
> b884f17df
- What is your RocketMQ version?
> 4.7.2
3. Other information (e.g. detailed explanation, logs, related issues,
suggestions on how to fix, etc):
Here is the debug log:
[14805_rocketmq-cpp.log](https://github.com/apache/rocketmq-client-cpp/files/4929539/14805_rocketmq-cpp.log),
the message consume callback is not returned during the whole log time range.
It seems the incorrect consume offset update happened somewhere between line
5906 and 6200
>5906: [2020-Jul-16 11:49:46.390552](info):oneway
updateConsumeOffsetToBroker of mq:MessageQueue [topic=dev-prefix-new-test,
brokerName=broker-0.rocketmq-dev-240-141, queueId=1], its offset
is:8036[updateConsumeOffsetToBroker:310]
>...
>6200: [2020-Jul-16 11:49:51.393309](info):oneway
updateConsumeOffsetToBroker of mq:MessageQueue [topic=dev-prefix-new-test,
brokerName=broker-0.rocketmq-dev-240-141, queueId=1], its offset
is:8037[updateConsumeOffsetToBroker:310]
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
