Aias00 opened a new issue, #10791: URL: https://github.com/apache/rocketmq/issues/10791
### What happened? `ClientManagerActivity.heartBeat` decodes the remoting request body with `HeartbeatData.decode(request.getBody(), HeartbeatData.class)` and immediately dereferences the result. `RemotingSerializable.decode` returns `null` for a null body, so a malformed `HEART_BEAT` request without a body can hit a `NullPointerException` and be reported as an internal proxy error. ### Why this matters The Proxy client-management path is part of the Studio/Proxy Admin foundation. Malformed client heartbeat frames should be rejected with a clear response code and remark instead of surfacing as an internal exception. ### Expected behavior Proxy should return a deterministic `INVALID_PARAMETER` response for empty or undecodable heartbeat bodies and must not register producer or consumer channels for that request. ### Scope RocketMQ Studio track 2 / Proxy client management hardening. -- 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]
