[Bug] Proxy gRPC converter should tolerate malformed timer properties

[Aias00]

Bug description

GrpcConverter.buildSystemProperties parses timer message properties with Long.parseLong when building the gRPC SystemProperties.delivery_timestamp field:

• MessageConst.PROPERTY_TIMER_DELAY_SEC
• MessageConst.PROPERTY_TIMER_DELIVER_MS

If either property is present but malformed, buildMessage can throw NumberFormatException while converting a Broker MessageExt into the gRPC v2 Message response. This can make a single malformed timer property fail the whole gRPC message response/query conversion path.

Expected behavior

The converter should tolerate malformed optional timer properties. Valid timer properties should still set delivery_timestamp; malformed values should be ignored with a diagnostic warning instead of failing the message conversion.

Affected area

proxy module, gRPC v2 message conversion.

Suggested fix

• Parse timer properties through a safe helper.
• Keep existing behavior for valid PROPERTY_TIMER_DELAY_SEC and PROPERTY_TIMER_DELIVER_MS values.
• Ignore malformed values and log a warning with diagnostic context.
• Add unit tests for valid and malformed timer properties.

[RockteMQ-AI]

Issue Evaluation

Category: type/bug | Status: Confirmed

The reported issue has been verified against the current codebase.

Root Cause: GrpcConverter.buildSystemProperties() (lines 194, 200) calls Long.parseLong() on PROPERTY_TIMER_DELAY_SEC and PROPERTY_TIMER_DELIVER_MS without catching NumberFormatException. A single malformed timer property in a MessageExt will crash the entire gRPC message conversion path.

Impact: Proxy gRPC v2 message conversion — any message with malformed timer properties will cause the conversion to fail with an unhandled exception.

Severity: medium

An automated fix proposal will be generated. Reply /approve to proceed with PR generation.

---

Automated evaluation by RockteMQ-AI