guyinyou opened a new issue, #7437: URL: https://github.com/apache/rocketmq/issues/7437
### 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/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/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. ### Runtime platform environment Linux ### RocketMQ version 5.1.5 ### JDK Version JDK11 ### Describe the Bug A shutdown occurs when the message is not completely written, causing all characters at the end of the message to be unwritten.  recover uses magicCode and bodyCrc to verify whether the writing is successful, but properties do not participate in the verification and belong to the end of the entire message. Therefore, it cannot be verified that the data of this message is wrong. If you continue to use this error message, unpredictable consequences will occur, such as blocking timerMessage distribution. ### Steps to Reproduce When there is an abnormal downtime, the body of the last message is written successfully, but the properties are not written successfully. ### What Did You Expect to See? During recover, data abnormalities in any part of the entire message can be verified. ### What Did You See Instead? Exceptions other than the body field cannot be found during recover. ### 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
