|
|
Service Package formUse the Pooling tab to configure a requestor pool for the services in this service package when they are stateless and unauthenticated. This tab is disabled if, on the Context tab, the Processing Mode field is set to Stateful or the Requires authentication? option is selected.
For information about requestor pooling, see Concepts — How requestor pooling for services works.
Field |
Description |
| Maximum Idle Requestors |
Specify the maximum number of idle requestors that can be in the pool for services from this package. If an active requestor becomes idle and is returned to the pool when the current number of idle requestors is at this limit, the requestor is deleted. To allow an unlimited number of idle requestors, set this value to -1;, the system does not delete idle requestors until they time out. |
| Maximum Active Requestors |
Specify how many concurrent requestors can be created and in use for the services in this package. Set this value to 1, even if you have disabled requestor pooling (that is, Maximum Idle Requestors is set to 0). If a service request arrives when the number of active requestors is at this limit, PRPC waits for an idle requestor. It does not create a requestor for the request. To allow an unlimited number of active requestors, set this value to -1. |
| Maximum Wait (in seconds) |
Specify how long, in seconds, PRPC will wait for a requestor return to the pool when a service request arrives but the number of active requestors has reached the Maximum Active Requestors value. If this time interval passes before any requestor returns to the pool, the request fails. PRPC then sends a failure message to the external client system. If the value of Maximum Active Requestors is set to -1, the value in this field is not meaningful, because requests never wait. If the pool has no idle requestors, PRPC creates a new one. |
About Service Package data instances