Wednesday, November 18, 2009

Connection Pooling

Some things after discovering look trivial and clear, but it takes time to find this simple reason. I found a lot of question in Internet, and almost no useful answers.

After SQL server restart you might get the error in your ASP.NET application: "A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) "

The reason is hiding in SQL Server Connection Pooling

You can do a simple test by adding ;Pooling=false to your connection string to Sitecore databases and now your application will not crash whenever SQL restarts.

Impact Connection Pooling on performance for a stand-alone Sitecore installation - is what I will try now to investigate.


thalluz said...

Great post, we've seen this message a few times, and cursed it to hell. Although waiting a few minutes did the trick. Lets have a look at the performance issues there could be on an installation. I could only imagine that the connections will be slower to initialize/release

Dmitry Vasilinenko said...

To keep updated: currently it's reported to product development for considering an improvement.