The concurrent manager has timed out waiting for the Output Post-processor

In this Document

Purpose

Troubleshooting Steps

References

---

APPLIES TO:

BI Publisher (formerly XML Publisher) - Version 12.0 to 12.0 [Release 12.0]
BI Publisher (formerly XML Publisher) - Version 11.5 to 11.5 [Release 11.5]
BI Publisher (formerly XML Publisher) - Version 5.6.3 to 5.6.3 [Release 5]
Information in this document applies to any platform.
Reviewed for relevance 19 Sep 2014.
Reviewed for relevance 2 Apr 2016.

PURPOSE

This document is intended for System Administrators. This note is generic in nature and is not designed to address product-specific issues. Individual product data is to be addressed by the product team that owns the XML data.

The purpose of this document is to outline bugs/patches, notes, knowledge base, and community resources for addressing the warning "The concurrent manager has timed out waiting for the Output Post-processor to finish this request."

The errors occurs when the time set for the final output file exceeds the amount of time specified in the time set for processing the request.  This is the amount of time the manager will wait for the OPP to actually process the request.

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



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


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.

Setting these profiles will allow a System Administrator to control the timeout value of the the OPP.  
Some reports like e.g. Create Accounting are expected to take up quite some time in the post 
processing phase and every customer trying to do so will hit a timeout the first time they try to run such a job.  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 will contain the warning.

The default value of the Concurrent:OPP Process Timeout profile option should be increased as it is not reasonable to assume that 99% of our seeded reports are expected to take up only a maximum of 5 minutes. Small reports based upon XML Publisher are typically embedded directly with in the application (Oracle Forms, OA Framework) whereas the larger reports are executed via Concurrent Processing hence the need to increase the default timeout value.


To obtain the Output Post Processor Request log file, follow the navigation below:
1.  Select the System Administrator responsibility.
2.  Select the menu Request - View.
3.  Select the Find button.
4.  Select the XML Publisher report that completed with warning.
5.  Select the View Log button.
6.  The log file will contain a warning similar to the following:

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

TROUBLESHOOTING STEPS

This error can be resolved by performing the following steps:
1.  Navigate to the System Administrator Responsibility.
2.  Then to Concurrent - Manager - Administer.
3.  Insure the OPP manager is running.
Note: If the OPP manager is not running then navigate to the Oracle Applications Manager responsibility - Concurrent Managers - Select Output Post Processor - View Details - Stop and then Start the Manager again.
4.  Navigate to Profile - System.
5.  Query the Concurrent:OPP Process Timeout profile option.
6.  Increase the timeout value (in seconds).
Example: If the current value is 120 then set it to 240. (Value *2).
Note:  We recommend setting the profiles to the following values to minimize seeing the occurrence of the Warning in your log file, especially if you are submitting large reports:
Concurrent: OPP Processing Timeout to 86400 (24 hours)
Concurrent: OPP Response Timeout to 3600 (1 hour)
7.  Bounce the concurrent managers and resubmit.

Note:  Insure the latest ATG RUP patch has been applied in your environment for better report processing performance.
Reference:
Note 1138602.1 -  Overview of Available Patches for Oracle XML Publisher (embedded in Oracle E-Business Suite)

Overview of Bug/Patch References:

Oracle E-Business Suite 12i:
     Bug 5588958     ATG120XB14NFUNC:HELP REPORTS NOT GETTING GENERATED
     Bug 6884508     ST1:XML:ITEM TEMPLATE LISTING (XML) IS COMPLETING WITH 
      WARNING
     Bug 7194171     COE: ARXCCS_XML: REPORT COMPLETES WITH WARNING FOR 
       LARGE DATA VOLUME
     Bug 7197625     ST3:XML:JOURNALS - LINE (XML) - REQUEST ENDING IN 
       WARNING
     Bug 9277468     JOURNAL ENTRIES REPORT PERFORMANCE PROBLEM
     Bug 9285528     REPORT FAILS TO GENERATE OUTPUT FOR HUGE DATA
     Bug 10144375  AP TRIAL BALANCE COMPLETE WITH WARNING OPP RESPONSE 
       TIMEOUT
     Bug 10176789   SUN: PURCHASE PRICE VARIANCE REPORT ERRORS


Oracle E-Business Suite 11i:
      Bug 5473035    After OPP Process Times Out Next Request Incorrectly Ends in Warning


Note References:
     Note 352518.1    Concurrent Request Fails Due to Timeout of the Post Processing Action 
     Note 364547.1    Troubleshooting Oracle XML Publisher For The Oracle E-Business Suite
     Note 428536.1    Concurrent Manager Has Timed Out Waiting For The Output Post-Processor 
     Note 1062578.1  CSTCRACC: Create Accounting - Cost Management - You Cannot
     Print the Report/Output
     Note 1069240.1   IRP5 and IT3A - NO OUTPUT FILES BEING GENERATED DURING
     PROCESSING
     Note 1142073.1  Serial Number Detail (XML) Errors Out With Concurrent Manager Has 
     Timed Out Waiting For the Output
     Note 1186853.1   EEO-1 Exception Reports Errors Out With REP-3000 and Current Manager
     Timed Out
     Note 1224684.1   AP Trail Balance Complete with Warning the Output Post Processor is
       Running but Has Not Picked Up this Request

ADDITIONAL RESOURCES FOR BI Publisher/XML Publisher

• SEARCH our BI Publisher knowledge area for a response to your issue [Navigation in My Oracle Support: “Knowledge” Tab then type “BI Publisher (formerly XML Publisher)” in “Select Product” then click to go to knowledge].
  
  
  • Please search on only the relevant information, use KEYWORDS and ERRORS, and do not include pronouns, conjunctions or prepositions unless it is part of the error message that is generated.
    
    
• Do you have a question about BI Publisher (install, setup, usage, etc.) or need a clarification about a BI Publisher note, bug, patch or certification? If YES, you should look inside our BI Publisher community under Discussions, Tips and Tricks, White Papers or start a new Discussion yourself. 
  
  
  • This community offers 24-hour turn-around responses (Monday to Friday) to your most pressing questions and concerns. It also lists our previously recorded and planned future Webcasts.

• For more information on BI Publisher Product documentation, Announcements, Hot Topics, Community, Blog and Training details. Take a look at the Oracle BI Publisher (BIP) Product Information Center (PIC) (Doc ID 1338762.1).

 

Attention :

This Note is in archived Status, which means that it is only available for historical purpose and that it is not maintained anymore.

Note 352518.1

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/22816976/viewspace-2085571/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/22816976/viewspace-2085571/