开发者社区> 李博 bluemind> 正文

如何处理不能正常开启 workflow mailer service 问题

简介:
+关注继续查看

Unable to Start Workflow Mailer Service (Doc ID 856229.1)  2011-12-28 11:44:41|  

Applies to: 
Oracle Workflow Cartridge - Version: 11.5.10.0 to 12.0.6 - Release: 11.5 to 12
Information in this document applies to any platform.
Symptoms
When trying to start the Workflow Notification Mailer, the following error occurs:
 
Error:
The service container is not running.
Additional information:
1) Workflow Mailer Service is down (Actual: 0, Target: 1), and when trying to start it, it remains down.
2) Workflow Agent Listener Service is up and all the corresponding listeners (workflow deferred agent listener, workflow java deferred agent
listener...) are up and running.
3) Debug service log (DebugSvcXXXXXX.txt) shows the following error:
 
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor80]
376700K->376655K(380160K), 0.6887140 secs]
Exception in thread "Cache Stats Writer" java.lang.OutOfMemoryError: Java heap
space
Cause
The memory allocated to mailer service is 384 MB which is too low.
This value can be seen in FNDSM log. When ICM diag is enabled, FNDSM log shows the command used to start mailer service:
AQCART: /u01/TEST/12.0.4/inst/apps/TEST_fin/admin/scripts/java.sh -server 
-Xmx384m -XX:NewRatio=2 -XX:+UseSerialGC -Doracle.apps.fnd.common.Pool.leak. 
mode=stderr:off -verbose:gc -Ddbcfile=/u01/TEST/12.0. 
4/inst/apps/TEST_fin/appl/fnd/12.0.0/secure/TEST.dbc -Dcpid=649255 -Dlogfi 
le=/u01/TEST/12.0.4/inst/apps/TEST_fin/logs/appl/conc/log/FNDCPGSC649255.t 
xt ...

-Xmx384m entry refers to the memory allocated to workflow mailer service.
Solution
Increase the memory allocated to mailer service by following the steps from Document 444939.1 How do you Change the Maximum Memory Size taken by
Workflow Service Container?
In a first step, set it to 512 MB and retest.
 
-------------------------------------------------------------
Solution

1. Modify parameter APPSJREOPT in $APPL_TOP/admin/adovars.env on the Concurrent Manager node to change the maximum memory size of the Workflow Services JVMs.

 For example, to limit the size to 512 MB, replace: 

APPSJREOPT="" 
export APPSJREOPT

with: 
APPSJREOPT="-Xmx512m" 
export APPSJREOPT
 
2. Bounce the Concurrent Managers to allow the change to take effect.
本文转自ITPUB博客tolywang的博客,原文链接:如何处理不能正常开启 workflow mailer service 问题,如需转载请自行联系原博主。

版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。

相关文章
k8s service资源定义详解
详解Service类型的资源定义
38 0
K8S 集群核心概念 Service 通过命令行创建 Service | 学习笔记
快速学习 K8S 集群核心概念 Service 通过命令行创建 Service
77 0
K8S 集群核心概念 Service 删除 Service 及学习总结 | 学习笔记
快速学习 K8S 集群核心概念 Service 删除 Service 及学习总结
764 0
Linkerd Service Mesh 授权策略(Server & ServerAuthorization)
Linkerd Service Mesh 授权策略(Server & ServerAuthorization)
51 0
Android源码分析--Service的启动和绑定
Android源码分析--Service的启动和绑定
142 0
Service中是如何产生ANR的?
Service中是如何产生ANR的?
113 0
SAP OData service的执行是如何从Gateway系统转交到backend系统
SAP OData service的执行是如何从Gateway系统转交到backend系统
48 0
如何处理SAP Fiori gateway service使用过程中遇到的404 error
Created by Jerry Wang, last modified on Nov 03, 2014
82 0
Kubenetes里pod和service绑定的实现方式
Kubenetes里pod和service绑定的实现方式
141 0
找出OData service出错根源的小技巧
SAP的Fiori应用是通过OData和后台交互的。在使用Fiori应用时您可能会遇到这样的错误消息: 这个错误消息没有包含有助于partner或者客户定位问题根源的线索。 下面是如何在后台找出问题根源的步骤。
1161 0
+关注
李博 bluemind
云栖社区Java、Redis、MongoDB运营小编,有意合作请联系钉钉:15810436147
文章
问答
视频
文章排行榜
最热
最新
相关电子书
更多
《基于 Service Worker 实现在线代理》
立即下载
开源广进-用Service Catalog构造K8S服务能力
立即下载
Data as a Service - 数据即服务
立即下载