Odd one.
My company has a large and cumbersome classic ASP application that has to run under a classic piplelined .net 2.0 appPool. InProc sessions are used to maintain connectivity between the client and the specific server that they are using (becomes a PITA when taking a server out of the balanced pool for maintenance).
We are currently investigating reducing the session timeouts in order to increase security and as part of this process I am looking at the perf counters to identify session duration.
On a nightly basis, a scheduled IIS stop/start is run (not a restart) to perform various automated maintenance tasks which should reset any existing connections to the server.
Looking at the 'Session Duration' Active Server Pages counter, the maximum session duration is 202,393,446 milliseconds (seehttps://technet.microsoft.com/en-us/library/cc781003(v=ws.10).aspx table D34) which is roughly in the order of 2.5 days.
How is this possible?