Alleviating long-running and long-pending requests

You might encounter concurrent managers with excessive waiting times caused by long-running or long-pending requests. The following information describes some of the methods you can use to alleviate long-running or long-pending requests.

To alleviate a long-running request

A long-running request can be caused by many different factors. The following information describes some of the methods you can use to alleviate a long-running request:

• A request that crosses the long-running threshold can be a concurrent request that requires an extended amount of run time. You can continue to let it process, or kill the concurrent request in Oracle Applications.
• You can determine the amount of time that a specific concurrent request normally requires to run. For more information, refer to Determining-concurrent-request-history.
• You can customize the long-running threshold for concurrent requests that historically require an extended amount of run time. For more information, refer to Setting-thresholds-for-concurrent-requests.
• You can alleviate the issue in Oracle Applications by adding a dedicated concurrent manager, adjusting work shifts and target processes, or scheduling the request to run when the concurrent request activity level is low. Work shifts are assigned to concurrent managers and the number of target processes is assigned to the work shift.

To alleviate a long-pending request

A long-pending request can be caused by many different factors. The following information describes some of the methods you can use to alleviate a long-pending request:

• At peak processing periods of the work shift, concurrent requests can cross the long-pending threshold.
• You can identify the requests that are running and pending. For more information, refer to Identifying-running-and-pending-requests.
• You can customize the long-pending threshold. For more information, refer to Setting-thresholds-for-concurrent-requests.
• If you have customized the long-pending threshold to a short amount of time, ensure that it exceeds the Internal Manager Sleep Time (30 seconds) so that the two values are not conflicting each other. The Internal Manager Sleep Time is a static value set by Oracle Applications and is listed in the OA_CONM application InfoBox.
• A long-pending request can be caused by a bottleneck. For more information, refer to Managing-bottlenecks.
• You can alleviate the issue in Oracle Applications by adding a dedicated concurrent manager, adjusting work shifts and target processes, or scheduling the request to run when the concurrent request activity level is low. Work shifts are assigned to concurrent managers and the number of target processes is assigned to the work shift.