IIS, dotNet, and App pool recycling

Thanks, Joe.

 

I found your posting about graceful Server shutdown just moments after I posted this. I've been using it with great success over the past few days, but it has raised a few questions.

 

I have to admit I don't quite understand the three 'states' that a pool member can be in - the 'Enabled' state is easily understood, as is 'forced offline', however, the 'disabled' state is where I'm tripping up.

 

When we say 'active' connections, is that something that is defined by a connection with data travelling back and forth every so often ? What determines the 'every so often' intervals ?

 

 

In practice, what I see is when I use the script to do a graceful shutdown of my pool members is that the great portion of the connections quickly go away, the connection count drops rapidly, down to the last 6 or 10. These then 'hang on' for L-O-N-G periods. I'd guess I could tune this in a profile setting, at the Virtual Server level ?

 

 

thanks !!