High Memory Consumption of Workflow Monitor Agent in Production
Last updated on OCTOBER 24, 2016
Applies to:Siebel Workflow - Version 184.108.40.206  and later
z*OBSOLETE: Microsoft Windows 2000
Version: 220.127.116.11 
Database: Oracle 18.104.22.168
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.11
Checked for relevance on 22 July 2013
This document was previously published as Siebel SR 38-2193895290.
The memory consumption for the WF Monitor Agent running a policy program is growing at a rapid pace and not releasing any forcing us to have to recycle the component. I will attach the performance log to the FTP site called app-dqnw-013_perf_log.dbg.
I have included a .sf and xml to provide you the details.
Issue.sif has the workflow policy programs from the repository.
We have a policy based on the S_EVT_MAIL.X_SEQ_NUM_FLG. This policy is attached to a Monitor Agent. The monitor agent only processes this particular policy. The policy runs two workflow policy programs.
The critical workflow monitor agent parameters are as follows:
Sleep Time parameter is 10.
Action Interval parameter is 10.
I have attached a spreadsheet with all of the parameters.
The Policy is triggered by the BOECOM Create and Update workflow process.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms