Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout

• 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.

Cause A (CONC-PP NO RESPONSE)

The concurrent manager process generates the XML data file. Upon completion it will trigger the Output Post Processor in order to merge the XML data file and the template which was selected on the Submit Request form.

The number of concurrent requests that the Output Post Processor can handle in parallel depends upon:

• the number of Processes
• the number of Threads Per Process

The default values are 2 Processes and 5 Threads Per Process so a total of 10 reports can be processed in parallel.

In case there are other concurrent requests running which have already invoked the OPP then it might happen that no additional requests can be picked up for a period of time. The pending request will be picked up as soon as one of the running jobs completes. By default a timeout will occur if it takes longer then 120 seconds (2 min.) for the Output Post Processor to pick up the request from the concurrent manager process. In that case, the concurrent request will complete with status Warning and the request log file will contain Error Message A (see above).

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

If Option 2 is taken, remember to stop and restart the OPP for the change to be implemented

• 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.

Cause B (CONC-PP TIMEOUT)

Once the Output Post Processor picks up the request, the BI Publisher engine is invoked to generate the final output file. The time that this takes will depends on various elements such as:

• size of the XML Data File
• complexity of the template
• performance of the server
• ....

By default a timeout will occur if it takes longer then 300 seconds (5 min.) for the BI Publisher engine to generate the output file. The concurrent request will complete with status Warning and the request log file will contain Error Message B. 

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

• 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.

Cause C (CONC-PP NO RESPONSE and TIMEOUT)

The Output Post Processor (OPP) service is not picking up any new requests.
The Output Post Processor JAVA process is still running, but it is unresponsive. 

This can be due to errors in previous requests or just to the amount of time the manager has been running. The OPP becomes unresponsive (stale) after running for more than one week.

Solution C (CONC-PP NO RESPONSE and TIMEOUT):
To implement the solution, execute the following steps:

For 11i and 12i Environments:

1. Please run the Concurrent Manager Recovery feature to address any Concurrent Manager / Concurrent Processing issues within the Oracle Application Manager.
2. Resubmit report.

OR

For 12i Environments:

1. Apply R12.ATG_PF.A.DELTA.6 (7237006)
2. 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).