"Thread was interrupted from a waiting state" at DbConnectionPool.CleanupCallback

Question

"Thread was interrupted from a waiting state" at DbConnectionPool.CleanupCallback

Pedro Gonçalves 25

Hi,

I'm getting this error, and I'm not able to fix it, or even understand from where it comes.

I'm also sure that all my SqlConnection are instanciated with Using (VB.NET), so the Dispose should be called for every one.

Does anyone have an idea about the cause?

This error seems to start after upgraded the app from .NET Framework from 4.6.2 to 4.8.1. But, I'm sure it's a coincidence...

Source: mscorlib; Message: Thread was interrupted from a waiting state.; Data:; StackTrace:    at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
   at System.Data.ProviderBase.DbConnectionPool.CleanupCallback(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers();

Regards,

Pedro

P a u l 10,761 Reputation points

2023-09-22T16:50:32.7633333+00:00

Are you spawning any Threads in your app that you're manually .Interrupt()ing?
Pedro Gonçalves 25 Reputation points

2023-09-22T17:12:19.2166667+00:00

No Paul, I'm not.

It seems that something is doing that, but outside my app! Is that even possible? Is System.Data.ProviderBase.DbConnectionPool shared by several apps? If so, is there a way I can find who else is using it?
Jiachen Li-MSFT 34,221 Reputation points Microsoft External Staff

2023-09-27T09:02:07.6666667+00:00

Hi @Pedro Gonçalves ,

If multiple applications within the same AppDomain are using the same database provider and connection string, they will share the same connection pool.
Pedro Gonçalves 25 Reputation points

2023-09-27T09:39:19.5166667+00:00

Hi @Jiachen Li-MSFT ,

And how can I know/find which applications are running in the same AppDomain than mine?

I guess it is possible that there is another app running in the machine that uses the same database provider and connection string.

And how can I identify how or what is causing I get a "Thread was interrupted from a waiting state" exception at System.Data.ProviderBase.DbConnectionPool.CleanupCallback() function, and how can I fix it, or handle it as I catch this exception at the AppDomain.CurrentDomain.UnhandledException event, and my app terminates due to that?

And if this is caused by another app, which I can't control, how can I protect my ap from that?

I don't know if this relevant, but the app is running in a VM.

Can you help me?
Jiachen Li-MSFT 34,221 Reputation points Microsoft External Staff

2023-09-27T09:58:42.9666667+00:00

Hi @Pedro Gonçalves ,

First, you might consider using your database management system to monitor database connections.

The error message you provided indicates that a thread was interrupted from a waiting state, and it seems to be related to thread synchronization and resource cleanup. This error message doesn't directly point to a specific cause or issue related to System.Data.ProviderBase.DbConnectionPool since you upgraded the app from .NET Framework from 4.6.2 to 4.8.1.
Pedro Gonçalves 25 Reputation points

2023-09-27T14:17:25.2533333+00:00

Hi @Jiachen Li-MSFT ,

Yes, monitoring the database connections should give me list of active connection, but I can't say if those connections are from my app or not.

The connection pool is based on the connectring string literally, or by it's contents?

I mean, if I add the "ApplicationName=MyApp;" at the connection string, does this builds another pool from another app that the connection doesn't have that?

Meanwhile I found in the application log, that there were times in the past, before the Framework upgrade, entries with the same exception. So that means that the problem is not in fact new or started just after the upgrade.

I know the error message doesn't points who caused the error, but the erro is afecting my app and I need to mitigate it in a way that my app doesn't crash because of it.

In my view, there 2 options: the cause is in my app, and I need to find it, or the cause it's outside my app, and I need to mitigate it so it can't affect my app.

Every use of DbConnection in my app is protected with try/catch blocks, and are always instanciated with Using to ensure the connection is colosed and disposed.

It seems that the exception is caused in another thread, not handled by my app.

Can you help me find the cause, or propose a way to mitigate the issue so it wouldn't crash my app?
Jiachen Li-MSFT 34,221 Reputation points Microsoft External Staff

2023-09-28T09:53:56.5133333+00:00

Hi @Pedro Gonçalves ,

Glad to see you have found a solution, you can post your solution as answer. It will also help others to solve the similar issue.

1 answer

Your answer

P a u l 10,761 Reputation points

2023-09-22T16:50:32.7633333+00:00

Are you spawning any Threads in your app that you're manually .Interrupt()ing?
Pedro Gonçalves 25 Reputation points

2023-09-22T17:12:19.2166667+00:00

No Paul, I'm not.

It seems that something is doing that, but outside my app! Is that even possible? Is System.Data.ProviderBase.DbConnectionPool shared by several apps? If so, is there a way I can find who else is using it?
Jiachen Li-MSFT 34,221 Reputation points Microsoft External Staff

2023-09-27T09:02:07.6666667+00:00

Hi @Pedro Gonçalves ,

If multiple applications within the same AppDomain are using the same database provider and connection string, they will share the same connection pool.
Pedro Gonçalves 25 Reputation points

2023-09-27T09:39:19.5166667+00:00

Hi @Jiachen Li-MSFT ,

And how can I know/find which applications are running in the same AppDomain than mine?

I guess it is possible that there is another app running in the machine that uses the same database provider and connection string.

And how can I identify how or what is causing I get a "Thread was interrupted from a waiting state" exception at System.Data.ProviderBase.DbConnectionPool.CleanupCallback() function, and how can I fix it, or handle it as I catch this exception at the AppDomain.CurrentDomain.UnhandledException event, and my app terminates due to that?

And if this is caused by another app, which I can't control, how can I protect my ap from that?

I don't know if this relevant, but the app is running in a VM.

Can you help me?
Jiachen Li-MSFT 34,221 Reputation points Microsoft External Staff

2023-09-27T09:58:42.9666667+00:00

Hi @Pedro Gonçalves ,

First, you might consider using your database management system to monitor database connections.

The error message you provided indicates that a thread was interrupted from a waiting state, and it seems to be related to thread synchronization and resource cleanup. This error message doesn't directly point to a specific cause or issue related to System.Data.ProviderBase.DbConnectionPool since you upgraded the app from .NET Framework from 4.6.2 to 4.8.1.
Pedro Gonçalves 25 Reputation points

2023-09-27T14:17:25.2533333+00:00

Hi @Jiachen Li-MSFT ,

Yes, monitoring the database connections should give me list of active connection, but I can't say if those connections are from my app or not.

The connection pool is based on the connectring string literally, or by it's contents?

I mean, if I add the "ApplicationName=MyApp;" at the connection string, does this builds another pool from another app that the connection doesn't have that?

Meanwhile I found in the application log, that there were times in the past, before the Framework upgrade, entries with the same exception. So that means that the problem is not in fact new or started just after the upgrade.

I know the error message doesn't points who caused the error, but the erro is afecting my app and I need to mitigate it in a way that my app doesn't crash because of it.

In my view, there 2 options: the cause is in my app, and I need to find it, or the cause it's outside my app, and I need to mitigate it so it can't affect my app.

Every use of DbConnection in my app is protected with try/catch blocks, and are always instanciated with Using to ensure the connection is colosed and disposed.

It seems that the exception is caused in another thread, not handled by my app.

Can you help me find the cause, or propose a way to mitigate the issue so it wouldn't crash my app?
Jiachen Li-MSFT 34,221 Reputation points Microsoft External Staff

2023-09-28T09:53:56.5133333+00:00

Hi @Pedro Gonçalves ,

Glad to see you have found a solution, you can post your solution as answer. It will also help others to solve the similar issue.

Answer 1

Jiachen Li-MSFT 34,221 Microsoft External Staff

Hi @Pedro Gonçalves ,

Try add Pooling=False in your connection string.

With Pooling=False, each time you open a connection, it will create a new, separate connection to the database, and it won't be pooled for reuse. When you close the connection, it will be completely closed and won't be reused by other parts of your application.

Pedro Gonçalves 25 Reputation points

2023-09-28T09:41:23.3666667+00:00

Thank you @Jiachen Li-MSFT ,

I addded Pooling=False in the connection string. This way each time a connection is open, it is created a new separate connection to the database, and it won't be pooled for reuse.

It's not the solution I wanted, because it has a negative impact in the performance, but I've already implemented it as a workaround, and since then I'd no more exceptions.

Share via

"Thread was interrupted from a waiting state" at DbConnectionPool.CleanupCallback

1 answer

Your answer