Arbortext PE 子进程 Pool Management
A subprocess pool is a collection of identical Arbortext PE 子进程. Each 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 Arbortext PE 子进程 in the pool, and a collection of rules that determine which HTTP requests can be processed by Arbortext PE 子进程 in the pool.
Support for multiple Arbortext PE 子进程 pools offer two major advantages:
• Pools of Arbortext PE 子进程 can have different parameters, making it possible to have groups of Arbortext PE 子进程 with different behaviors.
• Arbortext PE 子进程 pools can be configured to reserve performance capacity by ensuring that requests of a particular type don't consume all available Arbortext PE 子进程.
Each Arbortext PE 子进程 pool provides the following capabilities:
• ensuring that a configured minimum number of Arbortext PE 子进程 are running.
• starting additional Arbortext PE 子进程 (up to a configured maximum number) upon request.
• limiting the number of Arbortext PE 子进程 that can be used to process queued transactions.
• terminating any Arbortext PE 子进程 that fails to respond to a request from the Arbortext PE Request Manager after a configured period of time.
• terminating Arbortext PE 子进程 that have been idle for more than a configured maximum period of time.
• terminating an Arbortext PE 子进程 and starting a new one (between requests to avoid disruption of processing) if an Arbortext PE 子进程 has been running for more than a configured maximum period of time.
Terminating an 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 Arbortext PE 子进程 are busy and the maximum number of Arbortext PE 子进程 are running.
Parent topic