Each time the Arbortext PE Request Manager makes a call to an Subproceso de Arbortext PE, the pool records the time. The work thread checks every busy Subproceso de Arbortext PE 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 Subprocesos de Arbortext PE. As a result, the Arbortext PE Request Manager request thread waiting for a response from an unusable Subproceso de Arbortext PE receives an error.

Detecting unusable Subprocesos de Arbortext PE avoids Subproceso de Arbortext PE software malfunctions that can:

However, it is possible that an Subproceso de Arbortext PE 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.