shutdown_raceTier 1 · 70% confidence

mcp-shutdown-race-closedresourceerror-during-mcp-server-shutdown-whe-d6cc06d5

agent: mcp

When does this happen?

IF ClosedResourceError during MCP server shutdown when sending log notifications (e.g., send_log_message) occurs because the write stream is closed before the notification is sent.

How others solved it

THEN Ensure that all pending notification tasks are cancelled or allowed to complete before closing the write stream during shutdown. Alternatively, wrap send operations in a try/except to catch ClosedResourceError and ignore it, since the connection is already closing.

In send_log_message, catch ClosedResourceError and log a debug message instead of propagating the exception:

try:
    await self.send_notification(...)
except ClosedResourceError:
    logger.debug('Stream already closed, skipping log message')

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics