Aias00 opened a new issue, #850: URL: https://github.com/apache/rocketmq-dashboard/issues/850
### What happened RocketMQ Studio NameServer write APIs accept JSON literal `null` request bodies: - `POST /api/nameservers/create` - `POST /api/nameservers/update` - `POST /api/nameservers/restart` - `POST /api/nameservers/upgrade` - `POST /api/nameservers/delete` The controller passes the DTO directly to `ClusterService`, and the service logs fields such as `command.getClusterId()` / `command.getAddr()` before any null guard. A null body can therefore fail as an internal `NullPointerException` instead of a structured 400 response. ### Expected behavior NameServer write APIs should reject missing or JSON `null` request bodies with a clear 400 response, and the service should also guard direct calls to avoid accidental NPEs. ### Why this matters This belongs to the RocketMQ Studio control-plane architecture and operations baseline. NameServer management is part of the unified cluster management surface, and invalid write requests should fail predictably. ### Scope RocketMQ Studio / track 1 control-plane NameServer management. -- 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]
