Every afternoon around noon to 3 we are getting errors on our website when we are doing crud operations on the database.
When we are creating or updating, the error is:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Another recent error that we hadn't ever seen is this:
Transaction (Process ID 61) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
We recently got about half a million more users to the web application and I suspect it is because many are using it after lunch.
I checked the database maximum connections:
And it is: 32767 which seems ample.
I have nothing in the web.configuration file regarding the maximum users.
I did read that you can add something like this to the web.config:
<applicationPool maxConcurrentRequestsPerCPU="100" maxConcurrentThreadsPerCPU="0" requestQueueLimit="5000"/>
Also, if I look at the task Manager on the server it shows right now (no problems now):
Physical Memory (MB)
Kernal Memory (MB)
up time: 1:23:31:31
commit (gb) 9/30
We are hosted on Rackspace using sql server 2008 and windows web server 2008 R2 Enterprise.
Service Pack 1.
system: Quad-core AMC Opteron(tm) Processor 2374 HE 2.49 Ghz (4 processors)
installed memory RAM: 15.5 GB
system type: 64-bit os
What advice do you have? Should I put something in my web.config for maximum concurrent connections? And if so, what?
What is the default maximum users and would not having enough cause this problem on saving in the dbf? How can I find out the maximum users on the web application?
Is this even a web.config issue or is it a database issue?