Frun1na opened a new issue, #4650: URL: https://github.com/apache/rocketmq-dashboard/issues/4650
### Environment * rocketmq-dashboard branch: rocketmq-studio (commit 5b761df8) ### What happened `rmqctl mcp stdio` is designed to be launched by MCP hosts, which typically stop stdio servers by sending SIGTERM. The command context created in `App.Execute` only listens for `os.Interrupt`, so SIGTERM keeps its default disposition: the process is killed immediately and the stdio proxy's deferred `MCPClientSession.Close()` (the `DELETE /api/mcp` session-management call) never executes. The Studio server-side session remains registered until it expires on its own. Reproduce: run `rmqctl mcp stdio` against a Studio server, kill the process with `kill -TERM <pid>`, and observe that no `DELETE /api/mcp` request arrives at the server (while `kill -INT` does produce one). ### What should happen SIGTERM should be caught in the command context so the stdio proxy exits gracefully and releases the server-side session, the same way Ctrl-C does. ### Additional context PR with fix and tests: #<BACKFILL_PR> -- 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]
