Users may notice that user sessions are not removed immediately after the user session has been idle for a time greater than the Idle Timeout set at the Intelligence Server level. However, after some time the user session is correctly removed as expected. The user sessions can be observed in the User Connection Monitor in Strategy Developer.
The reason for this behavior is because the Strategy Intelligence Server must periodically check all the open sessions to determine which ones have been idle for a time greater than the idle timeout set. In addition there are more than one timeout setting to be checked - the User connection Idle timeout (client connections from Strategy Developer and similar tools), the Web User connection timeout (applies to all connections made through the Web API) and the Scheduler Timeout for sessions created by the scheduler.
To avoid the timeout thread from repeatedly checking the sessions and holding on to resources, the Intelligence Server chooses the minimum of the Web User and User connection timeout setting to determine how frequently to check for timed out sessions. If both the settings are 0, a default of 5 minutes is used, or if either setting is 0, the non - zero setting is chosen as the interval between checks. The Intelligence Server creates a timeout task that executes a check and sleeps for the pre-determined interval before checking the timed out sessions again.
So for example, if the user session idle timeout (as well as Web User timeout) was set to 2 minutes and a user session was idled since 12:01:01 this session may not be terminated exactly at 12:03:01; however because the Strategy Intelligence Server does the check every two minutes, the corresponding termination could happen at any time from 12:03:01 to 12:05:01 depending on the exact time the previous check completed.
For more detailed information in Web, refer to below Technical Note:
KB12867: How timeout settings in MicroStrategy Web and the MicroStrategy Intelligence Server affect users in MicroStrategy Web
