首页 > 代码库 > Concurrent:OPP Response Timeout解决案例
Concurrent:OPP Response Timeout解决案例
完整图文版:http://note.youdao.com/share/?id=4fed991700c3eaa12f951d7bbe4f0e37&type=note
小强反映,很多跑的请求都是completed and warning状态。
我们View log看一下情况。根据下面粗体内容,大概可以知道,可能是并发管理器数量不够的问题。并且,日志提示我们,可以适当提高OPP Response Timeout的等待时间。
+---------------------------------------------------------------------------+
DJI SCM: Version : UNKNOWN
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XXPO_RECEIVE module: DJI_采购收料通知单
+---------------------------------------------------------------------------+
Current system time is 11-JUN-2014 18:59:45
+---------------------------------------------------------------------------+
**Starts**11-JUN-2014 18:59:46
**Ends**11-JUN-2014 18:59:46
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
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.
+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 11-JUN-2014 19:03:46
+---------------------------------------------------------------------------+
在kingnod顾问dba Jack的指导下,以及根据:
The Output Post-processor Is Running But Has Not Picked Up This Request.(文档 ID 1547102.1)
Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout(文档 ID 352518.1)
我们做了以下变更。
根据Option 1: Increase the value (in seconds) for the profile option ‘Concurrent:OPP Response Timeout‘.
System的profile:Concurrent:OPP Response Timeout 从120改到900
根据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 管理器的process从1改成5
并且在数据库执行了以下sql,这是管理器java内存值的修改。
update fnd_cp_services
set developer_parameters = ‘J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m‘
where service_id = (select manager_type
from fnd_concurrent_queues
where concurrent_queue_name = ‘FNDCPOPP‘);
commit;
即将J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m 改成了J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m。
启示:
这次的跑请求缓慢问题,是管理器数量不足,或者说,是预先设定的问题。
我们发现,还有很多管理器,数量是1的,也可以考虑整改得更大。
声明:以上内容来自用户投稿及互联网公开渠道收集整理发布,本网站不拥有所有权,未作人工编辑处理,也不承担相关法律责任,若内容有误或涉及侵权可进行投诉: 投诉/举报 工作人员会在5个工作日内联系你,一经查实,本站将立刻删除涉嫌侵权内容。