pilichoumao opened a new issue, #6316: URL: https://github.com/apache/rocketmq-dashboard/issues/6316
### Before Creating the Bug Report - [x] Searched issues and PRs. #5209 concerns version output, #6310 config output, and #5656 (incorporated into #5643) upstream error diagnostics. These do not handle failed writes to MCP stdio stdout. - [x] Defect in Studio rmqctl. - [x] Reproduced on current rocketmq-studio. ### Studio Version rocketmq-studio 5e4c39b053c35a5598cc79ff331b8a54e649d7b1, built from source. ### Runtime Environment macOS / Go, real App.Execute and MCP HTTP transport against an in-process endpoint, with a failing stdout writer. ### Connected RocketMQ Cluster No cluster or MySQL required: failure occurs in the local stdio bridge. ### Describe the Bug Response, notification and JSON-RPC error frame writes ignore errors. When the agent closes its stdout pipe, mcp stdio can report success and continue forwarding input despite no longer delivering results. ### Steps to Reproduce Run App.Execute(mcp stdio) with initialize, notifications/initialized and tools/list input; use a writer returning a broken-pipe error; capture HTTP POST/DELETE counts. ### What Did You Expect to See? A failed stdout write terminates the proxy with an error/nonzero exit, cancels in-flight calls, closes the session and stops forwarding further input. Clean EOF should still drain pending results/notifications. ### What Did You See Instead? Exit 0, two failed stdout writes, three HTTP POSTs (the complete handshake and tools/list), then session DELETE. All three stdout frame paths ignore failures. ### Additional Context Proposed scope: propagate output errors without replaying requests, and cancel/close session before waiting for workers on early exit. Close interruptible stdin on early exit to release its scanner. Preserve existing handshake order, clean EOF draining, sanitized upstream diagnostics and signal registration policy. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- 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]
