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