Issue:
Various programs (like the AP Trial Balance and Invoice Register Report) complete with a warning status. The log file shows the following error message:
Beginning post-processing of request xxxxxxx on node at xx-xxx-xxxx.
Post-processing of request xxxxxxx failed at xx-xxx-xxxx with the error message:
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:
The profile option "Concurrent:OPP Response Timeout" was set to too low a value.
The log file clearly mentions the need to increase the value of this profile option
Solution:
Increase the value of profile "Concurrent:OPP Response Timeout" at the appropriate level
Logon to the applications with "System Administrator" responsibility
Navigate to Profile -> System
Query up the "Concurrent:OPP Response Timeout profile option
Increase the setting value. For example--if set to 120 seconds you might increase the setting to 240.
Bounce the middle tier
Restarting the OPP and retest the issue.
If there is still a problem, follow the additional steps below which can improve the Output Post Processor (OPP) manager's performance and then obtain a new log file and OPP log for review:
Increase the number of Output Post Processors as follows:
Logon to Applications with "System Administrator" responsibility.
Navigate to Concurrent -> Manager -> Define.
Query up the "Output Post Processor" manager.
Click on "Work Shifts" and increase the number of processes. For example: If there is currently a setting of 2 processes then increase it to 4.
In the "Parameter' field insure you have the following value:
oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
Increase the value of the Concurrent:OPP Process Timeout profile option as follows:
Logon to Applications with "System Administrator" responsibility.
Navigate to Profile -> System.
Query for "Concurrent:OPP Process Timeout" profile option.
Increase the setting to a higher value. For example: setting the value to 3600 seconds = 1 hour.
Please insure the following settings:
Logon to Applications with "XML Publisher Administrator" responsibility.
Navigate to Templates -> Query up and open the template -> Edit Configuration -> FO Processing and insure you have the following settings:
Use XML Publisher's XSLT processor TRUE
Enable scalable feature of XSLT processor TRUE
Enable XSLT runtime optimization TRUE
Set the Temporary Directory to a valid path. (Under General properties in the same screen)
Insure the tmp directory has at least 5GB of free space or 20 times more than largest data file running.
Change the heap size for the concurrent process (If memory errors are occurring during XML data generation)
Under Concurrent > Program > Define, query for the Accounts Payable Trial Balance program.
In the 'Options' field change the value to -Xmx1024M (or higher).
Restart the concurrent manager so that changes take effect.
Reference:
R12: Various Programs End With Warning: The Output Post-processor is Running But Has Not Picked up This Request (Doc ID 1224684.1)
Various programs (like the AP Trial Balance and Invoice Register Report) complete with a warning status. The log file shows the following error message:
Beginning post-processing of request xxxxxxx on node at xx-xxx-xxxx.
Post-processing of request xxxxxxx failed at xx-xxx-xxxx with the error message:
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:
The profile option "Concurrent:OPP Response Timeout" was set to too low a value.
The log file clearly mentions the need to increase the value of this profile option
Solution:
Increase the value of profile "Concurrent:OPP Response Timeout" at the appropriate level
Logon to the applications with "System Administrator" responsibility
Navigate to Profile -> System
Query up the "Concurrent:OPP Response Timeout profile option
Increase the setting value. For example--if set to 120 seconds you might increase the setting to 240.
Bounce the middle tier
Restarting the OPP and retest the issue.
If there is still a problem, follow the additional steps below which can improve the Output Post Processor (OPP) manager's performance and then obtain a new log file and OPP log for review:
Increase the number of Output Post Processors as follows:
Logon to Applications with "System Administrator" responsibility.
Navigate to Concurrent -> Manager -> Define.
Query up the "Output Post Processor" manager.
Click on "Work Shifts" and increase the number of processes. For example: If there is currently a setting of 2 processes then increase it to 4.
In the "Parameter' field insure you have the following value:
oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
Increase the value of the Concurrent:OPP Process Timeout profile option as follows:
Logon to Applications with "System Administrator" responsibility.
Navigate to Profile -> System.
Query for "Concurrent:OPP Process Timeout" profile option.
Increase the setting to a higher value. For example: setting the value to 3600 seconds = 1 hour.
Please insure the following settings:
Logon to Applications with "XML Publisher Administrator" responsibility.
Navigate to Templates -> Query up and open the template -> Edit Configuration -> FO Processing and insure you have the following settings:
Use XML Publisher's XSLT processor TRUE
Enable scalable feature of XSLT processor TRUE
Enable XSLT runtime optimization TRUE
Set the Temporary Directory to a valid path. (Under General properties in the same screen)
Insure the tmp directory has at least 5GB of free space or 20 times more than largest data file running.
Change the heap size for the concurrent process (If memory errors are occurring during XML data generation)
Under Concurrent > Program > Define, query for the Accounts Payable Trial Balance program.
In the 'Options' field change the value to -Xmx1024M (or higher).
Restart the concurrent manager so that changes take effect.
Reference:
R12: Various Programs End With Warning: The Output Post-processor is Running But Has Not Picked up This Request (Doc ID 1224684.1)