This attribute specifies the number of seconds that a thread will wait for allocation of an Arbortext PE sub-process. When a dynamic component calls com.arbortext.e3.E3RequestContext.allocateE3Subprocess, it will return immediately if it finds a free Arbortext PE sub-process in a pool that is configured to handle the HTTP request in progress. If no idle Arbortext PE sub-process can be found, allocateE3Subprocess will attempt to start a new Arbortext PE sub-process in the appropriate pool, provided the pool has fewer Arbortext PE sub-processes running than allowed by the pool's maxSubprocesses attribute. If no Arbortext PE sub-process can be started, then allocateE3Subprocess will wait until either an Arbortext PE sub-process is idle and available from the Arbortext PE sub-process pool or until the number of seconds specified by the maxSubprocessWait attribute have elapsed.

If the maximum number of seconds have elapsed and no Arbortext PE sub-process is idle, allocateE3Subprocess will throw an exception that no Arbortext PE sub-process could be allocated to serve the request. Processing at this point depends upon the dynamic component, but the component should return an error message to the client indicating that the request failed because no Arbortext PE sub-process could be allocated.

The default value is 300 seconds. You can set the value to 0 to disable the thread. Refer to Arbortext PE sub-process Allocation for a description of the allocation process.