I upgraded to 4.5.5 the other day from 4.4.1 and today was the first day with a heavy load of users. Twice today my SQL Server has crashed. Apparently, there are a lot of processes running on the sql server tieing up the CPU. The number of connection to the dotnetnuke database is in the hundreds. How is the connection pooling maintained? Is that done in the Microsoft.ApplicationBlocks.Data? Has that changed in this version?

Any insite would be much appreciated, I'm totaly in a panic!

Did you ever learn what was going on in your situation?

I have just run into something that may be similar and shed some light on what's happening. Using DNN 4.7 in our testing environment there are no problems. A pool of 18 connections is created, and those connections just keep getting reused as the sitegets browsed. However, when we move to the production environment, the connection pool just keeps growing until the limit is hit and the site crashes. The reclaimed connections lag way behind. The production environment in this case is 64-bit with 8CPUs and 16 GB RAM, whereas the testing environment is a 32-bit virtual machine.

As Cathal suggested, you can manipulate the size of the connection pool, and I have done that. Set it to 250. Then I can watch the connection pool on the web server grow right up to 250 and kill the site. The problem seems to be that the site is constantly creating new connections instead of reusing existing ones.

Is this a bug with ASP.NET in a 64-bit environment?

Tim