Scheduled pool start does not occur

Technical Note IRE2881
Created 03-Oct-2005

Applies To
Synapta Services Builder for 3270/5250 3.0

Session Allocation Manager

Pool Scheduler

Symptoms

Scheduled pool start does not occur

Pool fails to start on time.

Cause

The pool did not start after a scheduled stop and start because the time interval between the stop and the start was too low to allow the sessions (which had an UnrecognizedScreenException on the Login task reset path) to be cleaned up.
For example, if you have a pool of 25 sessions and the pool is set for the default initialization threads of 10, then the sessions will be closed in batches of 10, 10 & 5. If there is an UnrecognizedScreenException on the reset path of the Login task then there will be a 2 minute delay (default) in cleaning up the sessions which will effectively mean that the pool stop process takes approx. 6 minutes (2 minutes for each batch of closures).  If the pool start interval is less than the amount of time required for the pool stop process then the pool start will not occur.

Fix

Evaluate the amount of time it takes to close all of the sessions in the pool and make sure that the pool start time is set accordingly.