OPP time out 问题

  Symptoms

  Changes

  Cause

  Solution

    
Information Center, Diagnostics, & Community

  References

 

--------------------------------------------------------------------------------

 

Applies to:

Oracle Concurrent Processing - Version: 11.5.10.2 and
later   [Release: 11.5 and later
]

Oracle Concurrent Processing - Version: 12.0.0 and
later   
[Release: 12 and later]

Oracle Concurrent Processing - Version: 12.1.1 and
later   
[Release: 12.1 and later]

Information in this document applies to any platform.

Executable: XDOREPPB - Generate PDF from XML output and given
template

Concurrent Manager: Output Post Processor Output Post
Processor

Symptoms

A concurrent request fails to complete successfully due to a
timeout caused by the Concurrent Processing integration with BI
Publisher (formerly XML Publisher) functionality (patch
3435480).  Two possible errors may occur:

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.

Note: Review Solution C if increasing the Concurrent: OPP Response
Timeout or Concurrent: OPP Process Timeout did not resolve this
issue.

 

Changes

No specific changes have been made.

Cause

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

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 t
4000
he 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.

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

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:

Shutdown all concurrent managers and services.

Kill the FNDLIBR processes at the OS level, if needed.

Run the cmclean script. See document 134007.1 - CMCLEAN.SQL - Non
Destructive Script to Clean Concurrent Manager Tables.

Restart all concurrent managers and services.

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

Information Center, Diagnostics, & Community

Information Centers

E-Business Concurrent Processing Information Center Document
1304305.1

Please reference this document regularly to review current
offerings for Concurrent Processing needs.

Oracle BI Publisher (BIP) Product Information Center (PIC) Document
1338762.1

Please reference this document regularly to review current
offerings for BI Publisher needs.

Diagnostics

For additional help, please refer to one of the following documents
on diagnostics to address current needs. Providing diagnostic
output on an issue for support when logging a service request is
very helpful.

Document 179661.1 for 11i or Document 421245.1 for Rel 12.x

Core Concurrent Processing Community

Visit the Core Concurrent Processing community for help from
industry experts or to share knowledge.

BI Publisher Community

Visit the BI Publisher community for help from industry experts or
to share knowledge.

Consolidated: Document 553320.1, Document 1217683.1, Document
1226233.1, Document 553320.1, Document 1217683.1

References

BUG:4255934 - DCM WILL NOT DEPLOY APPLICATION

NOTE:1138602.1 - Overview of Available Patches for Oracle XML
Publisher embedded in the Oracle E-Business Suite

NOTE:291792.1 - Concurrent Processing - Using the Concurrent
Request Output Post Processor (OPP) in Oracle Applications

    相关内容
… 

  

   产品
… 

  

Oracle E-Business Suite > Applications Technology >
Application Object Library > Oracle Concurrent Processing >
Post-Processing > Post-Processing

Oracle E-Business Suite > Applications Technology >
Application Object Library > Oracle Concurrent Processing >
Post-Processing > Post-Processing

Oracle E-Business Suite > Applications Technology >
Application Object Library > Oracle Concurrent Processing >
Post-Processing > Post-Processing