My Oracle Support Banner

Workflow Monitor Agent (WorkMon) Component Crashes in DICIsColEncrypted() Due To S_LST_OF_VAL Volume (Doc ID 2737259.1)

Last updated on DECEMBER 15, 2020

Applies to:

Siebel Workflow - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Symptoms

Workflow Monitor Agent (WorkMon) shows high CPU after it starts processing data. After some time, the component will crash and exit.

Steps to Reproduce it:

1) Enable Workflow Component Group on the Siebel Server

2) Set the Group Name parameter for Workflow Monitor Agent

e.g: Group Name = ABC Group
       Default Task = 1

3) Start the component

4) The component starts and then crashes.

The following callstack is generated:

 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.