Concepts — How requestor pooling for services works

A requestor pool is a set of requestors that Process Commander reserves for use by the services in a specific service package.

Requestor pooling is available for stateless, unauthenticated service requests only. Requestor pooling often improves the performance of a service because requestors are reused, their allocated resources are shared, and the service need not wait for a requestor to be created.

How it works

The first time a service from the service package runs, Process Commander creates a requestor for it and creates the pool for the service package. When the service processing is complete, Process Commander adds the requestor to the pool.

The next time a service from that service package runs, Process Commander assigns the service a requestor from the pool if one is available. Otherwise, Process Commander creates and assigns a new requestor. When the service completes, Process Commander returns the requestor to the pool.

Requestors associated with a pool belong in one of two categories:

• Idle requestors are currently in the pool, waiting for a service request.
• Active requestors are currently out of the pool, managing service requests.

You specify how many requestors can be in the pool on the Pooling tab of the service package form. The setting for the number of idle requestors defines the size of the pool. The setting for the number of active requestors defines how many concurrent requestors you want to allocate to the services in the service package.

When the pool has no idle requestors, Process Commander continues to create new requestors for service requests until it reaches the limit specified for active requestors. If a service request arrives after that limit is reached and no idle requestors are in the pool, Process Commander waits to manage the request until an active requestor returns to the pool.

When an active requestor completes processing, Process Commander checks the limit for idle requestors before returning that requestor to the pool. If the pool is under the limit, the requestor becomes idle and Process Commander returns it to the pool. If the pool is at the limit, Process Commander deletes the requestor instead.

Testing

When testing or monitoring a service, you can examine the status of the requestor pool using the System Management application.

1. Start the System Management application. You may be prompted for authentication credentials.
2. Select a node.
3. From Select Administration >Requestor pools.
4. If desired, click a radio button for one pool. Click  Clear Requestor Pool   to terminate idle requestors for that pool.

About the System Management application About Service Package data instances

Concepts