delay in first call to web service

[Joe H]

i have a web service written in vb.net and hosted in asp.net under IIS 5. i
see a COM+ package in the Component Services explorer for this web service.
however, i never see a process ID associated with the COM+ package. the IIS
web site for the web service is set to run in High (Isolated) mode.

each time i make the first call to the web service, it takes forever to
respond and sometimes even times out. however, once it gets going it is
pretty fast. that is, until it goes idle again for a while.

is there any way to cure this problem? since it doesn't seem that the COM+
Leave Running When Idle option has any effect on the web service, is there
an alternative?

thanks,
joe

 

[Luke Venediger]

Hi,

The initial call of a webservice causes a lot of activity, and this activity
usually runs for more than your timeout period of 30 seconds or so.

The actual slow "initial startup" will happen under a few conditions:
1. Your asp.net worker process (aspnet_wp.exe under IIS5 and w3wp.exe under
IIS6) has not been started yet. This is due to an IIS restart or you have
not run any asp.net applications since the last time IIS was started.
2. The dlls of your service/application have changed and so the worker
process needs to reload them.

Hope this provides some insight

Regards,
Luke Venediger
http://blogdotnet.blogspot.com

 

[Joe H]

luke:

thanks for the reply. how does one go about stopping and starting a single
web service? i guess i am at a loss to understand the relationship between
the IIS MMC and the asp.net worker process. seems like i have to stop IIS
to get the asp.net worker process to stop? also, don't see why each web
service shows up in COM+, but i can't do anything with them there...

thanks,
joe