Complete Text Version: http://note.youdao.com/share? Id = 4fed991700c3eaa12f951d7bbe4f0e37 & type = note
Xiaoqiang reflected that many running requests are in the completed and warning status.
View log to check the situation. According to the bold content below, we can know that the number of concurrency managers may be insufficient. In addition, the log prompts that we can appropriately increase the waiting time of the OPP Response Timeout.
+ ------------------------------------------------------------------------- + Dji scm: Version: UNKNOWNCopyright (c) 1979,199 9, Oracle Corporation. all rights reserved. XXPO_RECEIVE module: DJI _ purchase receipt notice + hour + Current system time is 11-JUN-2014 18:59:45 + hour + ** Starts ** 11-JUN-2014 18:59:46 ** Ends ** 11-JUN-2014 18:59:46 + hour + Start of log messages from FND_FILE + upload ++ upload + End of log messages from FND_FILE + ----------------------------------------------------------------------- ++ upload + Executing request completion options... output file size: 779 + ------------- 1) PUBLISH ------------- +
Beginning post-processing of request 426785 on node ERP at 11-JUN-2014 18:59:46.
Post-processing of request 426785 failed at 11-JUN-2014 19:03:46 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.+ -------------------------------------- ++ ------------- 2) PRINT ------------- + Not printing the output of this request because post-processing failed. + -------------------------------------- + Finished executing request completion options. + response + Concurrent request completedCurrent system time is 11-JUN-2014 19:03:46 + ----------------------------------------------------------------------------- +
Under The guidance of kingnod consultant dba Jack, and according to: The Output Post-processor Is Running But Has Not Picked Up This Request. (Document ID 1547102.1) Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout (Document ID 352518.1) we have made the following changes.
According to Option 1: Increase the value (in seconds) for the profile option 'concurrent: OPP Response timeout'. the System profile: Concurrent: OPP Response Timeout is changed from 120 to 900
According to Option 2: Increase the number of processes or threads (or both) of the OPP via Oracle Applications Manager (see Note 291792.1 for the detailed instructions) output Post Processor manager's process is changed from 1 to 5
The following SQL statement is executed in the database. This is the modification of the manager's java memory value. Update parameters pai_parameters = 'J: oracle. apps. fnd. cp. gsf. GSMServiceController:-mx2048m' where service_id = (select manager_type from region where concurrent_queue_name = 'fndcpopp '); commit;
Change J: oracle. apps. fnd. cp. gsf. GSMServiceController:-mx512m to J: oracle. apps. fnd. cp. gsf. GSMServiceController:-mx2048m.
Revelation: this slow request execution problem is caused by the insufficient number of managers or preset problems. We found that there are still many managers with a quantity of 1, and we can also consider making bigger changes.
