Each time the Arbortext PE Request Manager makes a call to an Arbortext PE sub-process, the pool records the time. The work thread checks every busy Arbortext PE sub-process in its pool to see whether the time elapsed from the start of the operation has exceeded the configured maxBusyInterval attribute value (explained in The maxBusyInterval Attribute). If it has, the work thread sets a flag. Later, the work thread notifies the operating system to terminate these flagged Arbortext PE sub-processes. As a result, the Arbortext PE Request Manager request thread waiting for a response from an unusable Arbortext PE sub-process receives an error.

Detecting unusable Arbortext PE sub-processes avoids Arbortext PE sub-process software malfunctions that can:

However, it is possible that an Arbortext PE sub-process can't respond before the maxBusyInterval elapses, because it is processing a request that takes a long time. During your site setup, evaluate the requests likely to be submitted, and set the maxBusyInterval to a value that will allow lengthy jobs to complete.