Siebel AI Server Is Failing To Start Intermittently With Error "startup failed due to previous errors"
(Doc ID 2924435.1)
Last updated on FEBRUARY 06, 2023
Applies to:
Siebel CRM - Version 19.4 to 19.10 [Release V17]Information in this document applies to any platform.
Symptoms
Siebel AI server is failing to start properly during the enterprise restart which results in rejecting all incoming requests with 404 errors. This is happening intermittently. Below errors have been found in the AI tomcat logs.
localhost.<date>.log:
20-Jan-2023 05:14:27.107 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.filterStart Exception starting filter [SWSMFilter]
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at com.siebel.opcgw.utils.servicediscovery.ServiceData$ServiceNodeIterator.next(ServiceData.java:70)
at com.siebel.opcgw.utils.servicediscovery.RRLoadBalancingStrategy.getAvailableServiceNode(RRLoadBalancingStrategy.java:27)
at com.siebel.opcgw.utils.servicediscovery.ServiceDiscoveryInternal.getConnectString(ServiceDiscoveryInternal.java:208)
at com.siebel.opcgw.utils.servicediscovery.ServiceDiscovery.getConnectString(ServiceDiscovery.java:101)
at com.siebel.swsm.util.CGUtil.cgGet(CGUtil.java:41)
at com.siebel.swsm.config.CloudSourcedConfigReader.getGatewaySecurityProfile(CloudSourcedConfigReader.java:1071)
at com.siebel.swsm.config.SWSMConfig.initConfig(SWSMConfig.java:161)
at com.siebel.swsm.bootstrap.SWSMBoot.Initialize(SWSMBoot.java:144)
at com.siebel.swsm.bootstrap.SWSMBoot.init(SWSMBoot.java:99)
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:285)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:266)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4591)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5233)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:988)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1860)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Catalina.<date>.log :
20-Dec-2022 02:17:31.345 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/siebel] startup failed due to previous errors
20-Dec-2022 02:17:31.353 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [siebel] appears to have started a thread named [Thread-5-SendThread(PSBLGWY.tatasky.com:2320)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79)
sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:349)
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
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 |
| Cause |
| Solution |
| References |