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

If the maximum number of seconds have elapsed and no Subproceso de Arbortext PE is idle, allocateE3Subprocess will throw an exception that no Subproceso de Arbortext PE 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 Subproceso de Arbortext PE could be allocated.

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