A concurrent request fails to complete successfully due to a timeout caused by the Concurrent Processing integration with BI Publisher (formerly XML Publisher) functionality

ISSUE:

A concurrent request fails to complete successfully due to a timeout caused by the Concurrent Processing integration with BI Publisher (formerly XML Publisher) functionality

Error Message A (CONC-PP NO RESPONSE):

The Output Post-processor is running but has not picked up this request.
No further attempts will be made to post-process this request, and the request will be marked
with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.

Error Message B (CONC-PP TIMEOUT):

The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile.

Error Message C (CONC-PP NO RESPONSE and TIMEOUT):

The Output Post-processor is running but has not picked up this request.
No further attempts will be made to post-process this request, and the request will be marked
with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.

SOLUTION:

There are 2 new profiles options that can be used to control the timeouts. Depending on the error message, one of the following solutions needs to be implemented.

Profile Option : Concurrent:OPP Response Timeout
Internal Name : CONC_PP_RESPONSE_TIMEOUT
Description : Specifies the amount of time a manager waits for OPP to respond to its request for post processing.

Profile Option : Concurrent:OPP Process Timeout
Internal Name : CONC_PP_PROCESS_TIMEOUT
Description : Specifies the amount of time the manager waits for the OPP to actually process the request.

Note: The profile options are available as of $FND_TOP/patch/115/sql/AFCPOPRB.pls 115.3 and are included in Patch 4125550 11.5.10 CU2 for ATG Product family.

Solution A (CONC-PP NO RESPONSE)

Option 1: Increase the value (in seconds) for the profile option ‘Concurrent:OPP Response Timeout’.
Option 2: Increase the number of processes or threads (or both) of the OPP via Oracle Applications Manager (see document 291792.1 for the detailed instructions)

Note: The timeout profiles are set in seconds.
CONC_PP_RESPONSE_TIMEOUT: specifies the amount of time a manager waits for OPP to respond to its request for post processing.
CONC_PP_PROCESS_TIMEOUT: specifies the amount of time the manager waits for the OPP to actually process the request.
If Option 2 is taken, remember to stop and restart the OPP for the change to be implemented

Note: The same error may occur if the Output Post Processor is ‘hanging’, meaning that from the Administrator Concurrent Manager form the OPP does have 1 or more Active processes but no new requests are being picked up. In such case, the Output Post Processor must be restarted to restore the OPP functionality.

Solution B (CONC-PP TIMEOUT)
Increase the value (in seconds) for the profile option ‘Concurrent:OPP Process Timeout’.

Solution C (CONC-PP NO RESPONSE and TIMEOUT):

To implement the solution, execute the following steps:

For 11i and 12i Environments:
Please run the Concurrent Manager Recovery feature to address any Concurrent Manager / Concurrent Processing issues within the Oracle Application Manager.
Resubmit report.
OR
For 12i Environments:
Apply R12.ATG_PF.A.DELTA.6 (7237006)
Retest.
Workaround
The timeouts can also be altered directly in the package AFCPOPRB.pls :

The package body (AFCPOPRB.pls) and spec (AFCPOPRS.pls)can be found at the following location: patch/115/sql
Example: patch/115/sql/AFCPOPRB.pls

— Default timeout values for waiting on a response to a request (seconds)
TIMEOUT1   constant number := 120; 
TIMEOUT2   constant number := 300;
TIMEOUT1 and TIMEOUT2 corresponds to respectively OPP Response Timeout (solution A) and OPP Process Timeout (solution B).

Reference:

Concurrent Requests Fail Due To Output Post Processing (OPP) Timeout (Doc ID 352518.1)

  • March 7, 2019 | 18 views
  • Comments