Javacontainer2 Would Not Start After Increased the Default Task in SiebelRestCompIntMgr Component
(Doc ID 2691402.1)
Last updated on JULY 16, 2020
Applies to:Siebel CRM - Version 16.19 [IP2016] and later
Information in this document applies to any platform.
The environment has two javacontainer (javacontainer1 and javacontainer2) in the Siebel application server.
JavaContainer2 is not getting started after increased the component parameter Default Tasks(DfltTasks) to 2.
The issue can be reproduced at will with the following steps:
1. Have two javacontainer (javacontainer1 and javacontainer2)
2. Set DfltTasks in SiebelRestCompIntMgr to 2
3. Found that JavaContainer2 is not getting started.
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