The current design allows multiple hit processors and session archivers, but only one session closer. We suspect this may represent a processing bottleneck, particularly during service shutdown... when all active sessions are closed and their end-of-session events must be evaluated.

Note that when the active session count is high, canister manager shutdown may require more than 30 minutes. If the Windows service manager is used this will lead to a timeout and the service will be left in an unmanageable 'stopping' state.

This request is for Acoustic to verify that the session closer can restrict flow to the Long Term canister, both under high volume and when services are stopped. If the restriction is verified, an option for multiple session closers should be provided.

Possibly, there should also be an option to spawn these additional processes only during shutdown, to conserve CTree connections during normal processing.

One goal for this option is to provide for faster service cycling during patching, during the nightly service cycle, when configurations changes are deployed, etc..