Detecting Hung Sous-processus Arbortext PE
Each time the Arbortext PE Request Manager makes a call to an Sous-processus Arbortext PE, the pool records the time. The work thread checks every busy Sous-processus 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 Sous-processus Arbortext PE. As a result, the Arbortext PE Request Manager request thread waiting for a response from an unusable Sous-processus Arbortext PE receives an error.
Detecting unusable Sous-processus Arbortext PE avoids Sous-processus Arbortext PE software malfunctions that can:
permanently consume Arbortext PE Request Manager capacity (infinite loops, indefinite waits)
result in no response being returned to a waiting client
However, it is possible that an Sous-processus 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.
Est-ce que cela a été utile ?