Tom wilson wrote:
Yes, that sounds like it. But I'm having much trouble finding any
information on it. Searches for aspnet_state return hundreds of pages
telling me what it does (from the 'is it a worm?' aspect). I searched
for "Maximum number of worker processes". Google returns 3 hits.
There's an excellent page out there that tells me how to change the
values but not WHAT I should chnage those values to. Like:
<snip>
Do I change this? What do I change it to? What about the other
values? Do I change those and to what?
/Do/ you have "Maximum number of worker processes" set to more than one? You
might get answers from people more knowledgable in this are than me (not
difficult) in microsoft.public.inetserver.iis, but here's what I think the
settings do:
-------------------------
Recycling:-
Recycle worker processes: tear it down and start again just in case it's
gone messy somewhere. IME, in-process session-state gets destroyed when it
recycles a worker process.
Memory recycling: well, if it comes to that, either add more RAM or find the
memory leak. (Talking about memory, if the site seems sluggish, have a look
under the performance tab in Task Manager. If the total commit charge is
greater than the total physical memory then it wants more RAM.)
Performance:-
Idle timeout: shut it down after a while so that the next request after that
takes longer as it has to wake up again. This might also interfere with
session state (if so, look out for the session state timeout for the web
site - the setting you get to by right-clicking the web site, then
Properties->Home Directory tab->Configuration...->Options tab).
Request queue limit: reduce DOS attack effect.
CPU monitoring: what to do if it goes mad for too long.
Web garden: if one worker process gets stuck (see Recycling above), you can
have another one going so that people can still use the web site. Of course,
I should have put timeouts around all my requests to other services so it
didn't get stuck in the first place..
Health:-
Dunno, but if it ain't broke, don't fix it.
Identity:-
You might want to run the service under a different account from the
default, like you do with SQL Server etc. I've never tried that.
----------------------------
This article tells it all w.r.t. session state:-
http://msdn2.microsoft.com/en-us/library/ms178586.aspx
Oh - no it doesn't. It doesn't mention that with out-of-process
session-state you must make sure that everything you store in a Session()
variable must be <Serializable()as in
<Serializable()Public Class basketCentral
Implements IDisposable ' keeps it happy
......
And another thing: before wiggling all the bits, manually back up the config
by right-clicking on the computer in IIS Manager and going through All
Tasks..., and then back it up again when you've got it working
satisfactorily. If you have to re-install IIS, only the manually backed up
configs survive.
HTH
Andrew