11:44:39 AM
3K60P6807
Assuming your Web Connection apps run under the "Web Connection" Application Pool, any problem in the Default AppPool is not related to a problem by your Web Connection application. You can check what app runs under which appool either in the AppPool settings dialog or by clicking into the Application Pool in the list (Not sure if this works on 2003 - it does on IIS7+).
If it's one of the other AppPools the problem lies within there - possibly you're getting hammered with DOS attack? Have you chceked the IIS logs to see what's happening when you see these slow requests? Are you monitoring the CPU usage by the w3wp.exe instances?
Finally what other Web apps are running on this site and how resource intensive are they? Are they getting hammered by requests maybe to drive the Application Pool into high CPU use?
+++ Rick ---
No I'm not sure the problem is not in the network but where to look...I've power cycled everything that I can think of and the problem seems to still be there .
Is w3wp at fault, I do not know. I know after WC responds by showing a hit time, w3wp rises in task manager from very low in the list to second from the top (sort of columns is on CPU%) for the balance to the hit time. Then at about a split second after Web Monitor responds w3wp drops back down the list. Nothing else to go on.
I do not know if it matters but there are two copies of w3wp loaded, one is a SYSTEM user and the other which is the slow one sometimes is a NETWORK SERVICE.
After just noticing this, I lookes at Application Pools in IIS. I see that I have two defined, the DefaultAppPool which has two of the sites using and second one that is titled West Wind Web Connection. The two sites that seem to be having the intermittent long hit times are both listed under the DefaultAppPool. The DefaultAppPool is set to use the Identity "Network Service" while the West Wind app pool is configured for "Local System".
Oops, is this one of those many cases of users lack of reading the WC users manual? <s>
Any help that will speed up fixing the problem will as always be very appreicated!
--hm
You sure there isn't a problem with the network connection between the two machines? This sounds like the Internet Connection drops or dies for a few seconds before coming back.
What do you mean by 'when there is a problem with w3wp.exe? What problems do you see there?
+++ Rick ---
I've started to see a lot of long hit times, not in WC but in Web Monitor or the client browser. I'm running in File Mode on a 2003 server. The server is hosting five WC applicantions each of which has its own vfp. Each app has it own temp directory.
When it works correctly hit times in WC are around 0.2 - 0.4 seconds and Web Monitor reports about 0.4 to 0.8 second results. But when there is a problem with w3wp.exe (shown by watching in task manager processes), the hit times in WC are the same but Web Monitor shows 15-20 second results.
No known recent changes to anything on the server other than MS monthly Updates. System has been stable for several years.
Any thoughts?
West Wind Technologies
Making waves on the Web
from Hood River, Oregon