Hi,

The number of threads is determined by the agent/threadpoolsize and services/maxrequestorchildren environment settings that you configure in the prconfig.xml file.

1. Open the prconfig.xml file from the application server.

2. Add the following configuration:

   <env name="agent/threadpoolsize" value="xx" />

   <env name="services/maxrequestorchildren" value="xx" />

3. Save your changes and upload the prconfig.xml file to the application server.

threadpoolsize

Type: integer

Default: 5

Functionality: This setting entry adjusts the size of the batch requestor

pool, to provide the number of available Java threads on

which agents and batch requestors may run. The maximum number of threads is limited by the operating system

considerations.

maxRequestorChildren

Type: integer

Default: 10

Functionality: This setting limits the number of child requestors that can be

created for asynchronous connection processing. Ex: Run in Parallel in connectors or asynchronous API.

So the child requestors are batch requestors used for:

- explicitly started through the queueBatchActivity method in publicAPI

- implicitly started through the "run in parallel" option on Connect-SOAP, Connect-HTTP, Connect-REST, Connect-MQ, Connect-JMS and Connect-EJB activity methods.

- explicitly started through activity method Queue

- implicitly started through a parallel option in rule-declare-trigger

So - with the batch thread pool set at 200 you are allowing your PRPC server to run up to 200 agents and child requestors at the same time.

With maxRequestorChildren set to 100, you are allowing one requestor to have up to 100 explicit and implicit child requestors at the same time.

If you have more child requestor requests than threads, the child requests wait.

Thanks,
Lukasz