Repository navigation
number-of-active-connections metric goes negative, "activated multiple times?" debug assertions failing #3640
Description
Activity
Additional Info: In the process of writing this up, I noticed the PR Fix Debug Assertion in Connection Pool Due to Double Deactivation which appears not to be available in a public release yet.
I checked out the code from the
mainbranch, and indeed the debug assertion no longer fires. However, the metrics are still broken.As part of earlier testing, I slightly modified SqlClientMetrics.ExitActiveConnection to add a debug assertion, as follows:
internal void ExitActiveConnection() { DecrementPlatformSpecificCounter(ref _activeConnections); Debug.Assert(Thread.VolatileRead(ref _activeConnections) >= 0, "active connections must never be negative"); }
I find that this assertion still fires,
_activeConnectionsgoes to-1and presumably would go further negative if I let it run longer@mdaigle tagging you since this is familiar space for you.. could you please take a look?
Hi @borland, thank you for the report. I think I can see the issue. The commit you referenced adds an additional deactivation on this line: 0322d44#diff-9d38a50f1645237c63d8786c5f4b3251b91a2ecae192b899992e8cebc511d219R1808-R1811. However, at the point that that method is called, the connection has already been deactivated. This means that deactivations are getting double counted, resulting in negative active counts as transacted connections are recycled through the pool. I'll look into a fix for this that we can get backported to 6.1.
Note for other observers: I noticed 6.1.2 had been released, so I re-tested, and the bug is still present
- linked a pull request that will close this issue[6.1] Fix 3640 | Remove extra connection deactivation. #3776
on Nov 24, 2025
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Describe the bug
Since upgrading from SqlClient v6.0.2 to v6.1.1, we noticed in our metrics that the
number-of-active-connectionsstarted to report negative values, sometimes quite large -- e.g. -357Rolling back to v6.0.2 removed the issue.
I am not aware of anyone noticing any other problems with the 6.1.1 upgrade at this stage.
To reproduce
I am not sure what exactly in our codebase is triggering the buggy code path; Our application is quite large and complex, it opens many SQL connections rapidly.
However, I checked out SqlClient locally, built it as part of our application's solution, and used
git bisectto narrow down the commit which introduces the problem.When testing this, I found the debug assertion in DeactivateConnection would fire shortly after launching the application.
Expected behavior
Metrics should not go negative, debug assertions should not fire.
Further technical details
Microsoft.Data.SqlClient version: (found on the nuget or Microsoft.Data.SqlClient.dll)
.NET target: (e.g. .NET Framework 4.7.2, .NET 6.0)
SQL Server version: (e.g. SQL Server 2022)
Operating system: (e.g. Windows Server 2022, Ubuntu 24.04, macOS 14.7.1, Docker container)
Additional context
Our hosting platform runs Linux, and my local machine is a Mac with an M4 Max. I use JetBrains Rider to build and debug with .NET 8.0.413