Loyalty Component is not starting configured number of Tasks

(Doc ID 2124027.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Loyalty Manager - Version 15.4 [IP2015] and later
Information in this document applies to any platform.

Symptoms

On : 15.4 [IP2015] version, Loyalty

ACTUAL BEHAVIOR
---------------

The component eLoyalty Processing Engine - Batch Accrual is not starting the correct Number of Tasks.

3 MTServer
4 LOYEngineNumberOfTasks - number of threads

sometimes it starts 0, sometimes it starts like 7 tasks.


EXPECTED BEHAVIOR
-----------------------
It is expected that 15 threads are started.

1 MTServer > 4 thread + 1 = 5
2 MTServer > 4 thread + 1 = 5
3 MTServer > 4 thread + 1 = 5 Total of 15 threads


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. They copied OOTB "eLoyalty Processing Engine - Batch" component to "eLoyalty Processing Engine - Batch Accrual"

2. This component has:

Max and MinMTServer = 3
MaxTasks = 4

3. From UI (Admin - Server Manager) we can see that "eLoyalty Processing Engine - Batch Accrual" component is ONLINE

4. They have a bat file that call Server Manager (srvrmgr) to start the component "eLoyProcessing Engine - Batch Accrual" (enable comp)

5. then another bat to start the component using WkfProcMgr component Loy Engine - Start Engine Accrual

start task WkfProcMgr process_name = Loy Engine - Start Engine Accrual

6. From UI (Admin - Server Manager) we can see that "eLoyalty Processing Engine - Batch Accrual" component is RUNNING

7. However, in the UI we see that "Running" tasks = 7

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot have the correct number of tasks started causing Accruals not being processed

Cause

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