asp.net - Switched from inproc to SQL Server gives me SQL timeouts (no connection max pool size, typed datasets) -
Here's my status:
I have a web and database server (SQL Server 2005) .
Many applications pools and sites in the webserver (iis6) run fine with inpoc asp.net sessions, both server runs 2k3 win
Now I switch from SQL to inproc and I use SQL Timeout expired messages get lots of attention. But only from a web application that went to session on SQL Server. All other websites are not affected
Thank you in advance!
Best regards,
P>
JP
EDIT: As used by SQL Server Web's Web App Confidential request:
& lt; SessionState mode = "SQLServer" timeout = "60" sqlConnectionString = "data source = 192.168.1.80; constant security information = true; user id = espastate; password = state" />
I forgot to mention that the problem with the SQL Server website shares an application pool with a web application that runs inproc. I split just two web applications into my own app pool. But I do not think it will solve the timeout. The strange thing is that all other websites are working fine.
EDIT 2: I have received this message today when I tried to switch from encront to sqlserver as data access. I use all the typeDataSets (* .xsd), my web app is an e-commerce site, which has about 2k unique visitors a day, this message is:
Expired Has been able to get a connection from the pool The expiration period has expired. This could be because all the pool connections were in use and reached the maximum pool size.
This sounds like a specific application to connection connection leaks and connection pools Filling As a result of SQL Server timeout, tracing these issues can be extremely frustrating, take a look at a profiler application and tools such as.
Comments
Post a Comment