Subproceso de Arbortext PE Pool Management
A subprocess pool is a collection of identical Subprocesos de Arbortext PE. Each Subproceso de Arbortext PE pool has a unique name, a collection of attributes that describe the pool's behavior, a set of parameters that are passed to every Subproceso de Arbortext PE in the pool, and a collection of rules that determine which HTTP requests can be processed by Subprocesos de Arbortext PE in the pool.
Support for multiple Subproceso de Arbortext PE pools offer two major advantages:
• Pools of Subprocesos de Arbortext PE can have different parameters, making it possible to have groups of Subprocesos de Arbortext PE with different behaviors.
• Subprocesos de Arbortext PE pools can be configured to reserve performance capacity by ensuring that requests of a particular type don't consume all available Subprocesos de Arbortext PE.
Each Subproceso de Arbortext PE pool provides the following capabilities:
• ensuring that a configured minimum number of Subprocesos de Arbortext PE are running.
• starting additional Subprocesos de Arbortext PE (up to a configured maximum number) upon request.
• limiting the number of Subprocesos de Arbortext PE that can be used to process queued transactions.
• terminating any Subproceso de Arbortext PE that fails to respond to a request from the Arbortext PE Request Manager after a configured period of time.
• terminating Subprocesos de Arbortext PE that have been idle for more than a configured maximum period of time.
• terminating an Subproceso de Arbortext PE and starting a new one (between requests to avoid disruption of processing) if an Subproceso de Arbortext PE has been running for more than a configured maximum period of time.
Terminating an Subproceso de Arbortext PE avoids possible consumption of resources that could accumulate over time.
• returning messages that a request has failed after a configured interval if all Subprocesos de Arbortext PE are busy and the maximum number of Subprocesos de Arbortext PE are running.
Parent topic