Before Creating the Bug Report
Runtime platform environment
RocketMQ Nameserver, Broker, Proxy ran in linux container with Podman Desktop on MacOS.
Client ran on MacOS.
RocketMQ version
Broker 5.3.3, Client Java SDK 5.0.8.
JDK Version
JDK 21 Temurin-21.0.4+7
Describe the Bug
In particular sequence of operations, ack would not take effect nor throw exception.
Steps to Reproduce
- Create a topic that has 1 read queue and 1 write queue.
- Send 10 messages into the topic.
- Read the messages, for the 5th message, change its invisible duration and acknowledge it.
- Read the topic again, with the same consumer group.
What Did You Expect to See?
The acknowledged message would not be seen in the second read.
What Did You See Instead?
The acknowledged message was seen in the second read.
Additional Context
Test case:
rocketmq-test.zip
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
RocketMQ Nameserver, Broker, Proxy ran in linux container with Podman Desktop on MacOS.
Client ran on MacOS.
RocketMQ version
Broker 5.3.3, Client Java SDK 5.0.8.
JDK Version
JDK 21 Temurin-21.0.4+7
Describe the Bug
In particular sequence of operations,
ackwould not take effect nor throw exception.Steps to Reproduce
What Did You Expect to See?
The acknowledged message would not be seen in the second read.
What Did You See Instead?
The acknowledged message was seen in the second read.
Additional Context
Test case:
rocketmq-test.zip