ELBATCHES- Stuck Threads With Standalone Scheduler
(Doc ID 2876752.1)
Last updated on JUNE 15, 2022
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.4.0.0.0 and laterInformation in this document applies to any platform.
Goal
We have setup standalone scheduler and after the changes , EL Batches have performance issues.
Observed stuck threads on Scheduler managed server.
Below are the properties
SCECEJB_LOOKUP_TYPE=LOCAL
HOST_SERVER is the scheduler server
ELCM_PROVIDER_URL=Loadbalancer URL of FCUBS
In GETM_BLOCK_EXT_SYS_DETAIL , ELBATCH has been maintained with LB URL of FCUBS
We have around 650 branches and EOD is submitted with the same number of threads as that of branches. The quartz threads has been set to 650.
Before moving to standalone scheduler, scheduler was codeployed with FCUBS and ELCM batches were running fine. The scheduler was moved to standalone as part of OBPM recommendation.
How do we move the load of ELCM batches to FCUBS keeping the scheduler standalone ?
Solution
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
Goal |
Solution |
References |