HusterSL opened a new issue, #949: URL: https://github.com/apache/rocketmq-clients/issues/949
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Programming Language of the Client Node.js ### Runtime Platform Environment Windows 10 ### RocketMQ Version of the Client/Server Client/Server Rocket Version: 5.3.0/5.3.0 ### Run or Compiler Version Compiler: JRE 8.0 OS: Windows 10 ### Describe the Bug When FIFO messages are consumed by multi-SimpleConsumer, if a previous message in the message queue of the same message group is being consumed by one consumer and has not yet returned an ACK, subsequent messages may still be consumed by another consumer. This results in the inability to guarantee the order of messages in the same queue when consumed by multi-SimpleConsumer. ### Steps to Reproduce 1. Connect: Connect to the RocketMQ server using the rocket-client-nodejs; 2. Produce Message: the producer creates multiple message group messages and sends them to the corresponding FIFO-type topic on the server; 3. Consume Message: multi-SimpleConsumers simultaneously consume FIFO messages from the corresponding topic; 4. Observer the Result: It cannot be guaranteed that messages in the same message queue will only be consumed after the preceding messages have returned an acknowledgment (ack). ### What Did You Expect to See? When multi-consumer consume FIFO messages, guarantee that the subsequent messages can only be consumed after the previous messages have returned an ACK. ### What Did You See Instead? The FIFO Message Consumption Order Can be Guatanteed by Multi-SimpleConsumers in Nodejs-Clients. ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
