ASP.Net process idleTimeout not working

  • Thread starter Thread starter feng
  • Start date Start date
F

feng

I am trying to let ASP.Net process, aspnet_wp.exe, refresh
itself after being idle for 2 minutes by setting
machine.config's idleTimeout value. But this doesn't seem
to work. I tried several times and I am testing using
localhost, so I know it is really idle. When I am waiting,
I watch the running process ID for aspnet_wp.exe. It never
changes.

Am I mising something here?

Please help!

Thanks.
 
Hi Feng,
If you use idelTimeout ,what it will do is if the server has not served
any requests for the amount of time you specified which is 2 minutes then it
automatically shuts down the process.
Make sure you follow the format idleTimeout="00:02:00" for 2 minutes. In
your case the process could have been shut down after 2 minutes and no new
request came in afterwards.
That is why the running process ID is not changed.If a new request has come
afterwards a new process will start automatically.
If you need to recycle the ASP.NET process then you need to use
timeout.It will be timeout="00:02:00" ,this will create a new process after
2 minutes.The time clock starts
after the first request is made,because the process is created after the
first request to the ASP.NET engine is made.

Hope this helps.
Regards,
Marshal Antony
..NET Developer
http://www.dotnetmarshal.com
 
Thanks for your reply.

First of all, I can't use timeOut. It has to be
idleTimeout.

Secondly, the idleTimeout doesn't seem to work that way. I
tried as you said: send a request and wait for the
idleTimeout to expire. Then, while watching the
aspnet_wp.exe's process ID, I send a second request. What
I see now is that the process ID still remains the same.

Any ideas?
 
Feng,

I did some real testing and found that it is working.
Here are my findings regarding changing of processid.
If you set idleTimeout as 2 minutes,and if no request came in
for 2 minutes the process id will change(it will be in a idle
state).Afterwards if I send a request the process ID
remains the same(the process is automatically started).Then you need to
wait for another 2 minutes and if no request came in within 2 minutes a new
process id will be created.
This is what happens.I used Windows XP Professional and .NET Framework 1.1
for this testing.
To monitor the change of Process ID,go to command prompt and type
tasklist and look for the image name aspnet_wp.exe and look at it's PID.
Remember, it is advisable to do an iisreset after you change the
machine.config.For this,go to command prompt and type iisreset.
Hope this helps.
Regards,
Marshal Antony
..NET Developer
http://www.dotnetmarshal.com
 
Back
Top