dingshuangxi888 opened a new issue, #10082: URL: https://github.com/apache/rocketmq/issues/10082
### 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 develop ### JDK Version java11 ### Describe the Bug In GrpcConverter.buildSystemProperties() method, the message type detection logic for delay messages is incomplete. It only checks 3 out of 4 delay-related properties: ```java if (messageExt.getProperty(MessageConst.PROPERTY_DELAY_TIME_LEVEL) != null || messageExt.getProperty(MessageConst.PROPERTY_TIMER_DELIVER_MS) != null || messageExt.getProperty(MessageConst.PROPERTY_TIMER_DELAY_SEC) != null) { systemPropertiesBuilder.setMessageType(MessageType.DELAY); } ``` ### Steps to Reproduce xxx ### What Did You Expect to See? The message type detection should check all 4 delay-related properties, consistent with TopicMessageType.parseFromMessageProperty() implementation: ```java if (messageProperty.get(MessageConst.PROPERTY_DELAY_TIME_LEVEL) != null || messageProperty.get(MessageConst.PROPERTY_TIMER_DELIVER_MS) != null || messageProperty.get(MessageConst.PROPERTY_TIMER_DELAY_SEC) != null || messageProperty.get(MessageConst.PROPERTY_TIMER_DELAY_MS) != null) { // This is missing in GrpcConverter return TopicMessageType.DELAY; } ``` ### What Did You See Instead? xxx ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
