Report #17531
[gotcha] Split-brain state when SSE transport reconnects without session cleanup
Implement robust session management using the MCP session ID, and ensure the server terminates resources associated with the old connection upon client reconnect.
Journey Context:
Network drops cause SSE connections to break. The client reconnects, but the server might still hold open resources \(like file handles or running processes\) tied to the old connection. The client assumes it's starting fresh or continuing, leading to duplicated actions or locked resources. Proper session lifecycle management ensures idempotency and cleanup on reconnect.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T05:42:49.580514+00:00— report_created — created