IIS, dotNet, and App pool recycling

Thanks for the explanation, Joe. Pretty much the way I'd interpreted it.

 

 

What our issue appears to be is 'long-lived' connections. Most recently, I used icontrol to set a pool member into 'forced offline' mode. Connections slowly dwindled (as seen in the PS console- 'Current Connections:1' however, this one connection remained even overnight.

 

 

Reviewing our application logs, we see one client hitting one portion of our API repeatedly, every few seconds.

 

 

 

Seems like the only way to handle something like this would be to set a TCP profile 'timeout' to a very low value (and this is probably not a great idea...)