Hello Chris
Yes we have tweaked settings in our machine.config file per recommendations from Microsoft
we have set our maxWorkerThreads to 100 and maxconnection to about 2. We have tried changing the maxconnection attribute to 12 but we have not seen any improvement. our minFreeThreads is also set to 100
So far our web servers average on 4-6 deadlocks on a daily basis. Most notably during times of heavy usage
We call a webservices on a separate server. This server however also hosts 1 or 2 other webservices used by another application. These webservices occasionally call on a clustered database server to make queries
So far I do not see any attributable condition to our SQL Server database. Or could it have one
----- Chris Coffey wrote: ----
I am having a similar issue on a production server
Window 2000 Serve
4 pro
2 GIG RA
IIS 5.
the app works for a while and then gets the "Server Applicatio
Unavailable" message (always good to show customers). our app call
several webservices...i believe we are hitting a deadlock and i am no
sure how to resolve (not getting any application event log entries).
does your app call webservices? (may need to tweak th
<system.net><connectionManagement><add address="*" maxconnection="20"/> (default is 2
</connectionManagement></system.net
we tweaked the <processModel> attributes, but not th
"responseDeadlockInterval", b/c i believe it shortens or prolongs th
real problem....we did however increased maxWorkerThreads and saw som
improvement
i am not sure about the answer to your problem (does that mean tha
the process is stalled or that it has just restarted?)...but i have
call into microsoft and will post the answer when it's available
chri
------------------------------------------------------------------------
"Sefi" <is**************@yahoo.com.remove_this_antiSpam_t ag> wrote in message news:<62**********************************@microso ft.com>..
Good day everyone
I'm a bit confused about whether the "Server Application Unavailable" status of my website that frequently occurs when several users are simultaneously logged into it is a symptom that the asp.net worker process has restarted or that it is 'stalled' and is about to be restarted I read from techNet that I can tweak processModel attributes from my machine.config, particularly the attribute responseDeadlockInterval
The default setting for this is 3 mins. The article (http://www.microsoft.com/technet/tre...delelement.asp
says that I should consider increasing the interval if an ASP.NET application is causing the ASP.NET worker process to restart
My question is, when a user tries to enter my site and encounter
the "Server Application Unavailable" page, does that mean that th
process is stalled or that it has just restarted? If I wish to avoi
the above message from occurring, should I increase the interval fo
responseDeadlockInterval? But that would mean that users would no
have to wait a longer time before they can successfully load the site
And does this guarantee that they will successfully load the page if
set the interval to a long enough time to allow for queued requests t
get processed
THANK YOU very much for your insights