Fix stale database connections in async MCP handlers#4
Open
magent-cryptograss wants to merge 2 commits into
Open
Fix stale database connections in async MCP handlers#4magent-cryptograss wants to merge 2 commits into
magent-cryptograss wants to merge 2 commits into
Conversation
Same DEFAULT_EXEMPTIONS as secrets_filter.py - prevents redacting common non-sensitive values like database names (pickipedia, mediawiki, etc.)
When Django ORM queries are wrapped with sync_to_async in a long-running async process, database connections can become stale. This manifests as "connection already closed" errors when calling MCP tools. Solution: Add a with_fresh_connection wrapper that calls close_old_connections() before and after each database operation, ensuring a fresh connection for every MCP tool call.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
with_fresh_connectionwrapper that ensures fresh DB connections for each tool callRoot Cause
When Django ORM queries are wrapped with
sync_to_asyncin a long-running async process (like the MCP server), database connections can become stale between tool invocations. PostgreSQL connections time out, but Django's connection pool doesn't automatically detect and refresh them.Solution
Call
django.db.close_old_connections()before and after each database operation, forcing Django to establish a fresh connection.Test plan
bootstrap_memoryMCP tool