-
标题
Recycling Options for SCM IIS App Pools -
说明
Sensitive Content Manager's default recycling settings are inherited from the IIS Server default. Can the Idle Timeout or physical memory/request settings be modified for the Sensitive Content Manager IIS Pools? -
原因
SCM does not set explicit recycling limits and instead inherits these from the root IIS Machine level. -
解决办法
Sensitive Content Manager sites include a 'heartbeat' every 5 minutes to ensure Site and Application Pool health. As a result, Idle Timeouts can be set on each of these sites without the sites becoming disabled. We do not recommend setting an idle timeout lower than 10 minutes, as the Sites will not restart automatically on the submission of a scan.
Memory and Request limits can be created on an environment by environment basis. However, the actual limits may vary depending on the number of scans being performed, their complexity, and any SCM-related policies that exist on file modification or upload. Before changing these limits, please note the amount of memory regularly used by these pools, as a recycle can impact running scans or cause them to halt.