SES Application Container Fails to Start With JMS files
(Doc ID 2815710.1)
Last updated on OCTOBER 22, 2021
Applies to:
Siebel CRM - Version 21.4 and laterInformation in this document applies to any platform.
Symptoms
In Siebel 21.4 environment, Siebel server can not be started after JMS configuration is done by following the knowledge document below:
Setting Up And Using JAVA64 Named Subsystem For Siebel EAI JMS Transport (Doc ID 2332726.2)
After analyzing the log files, SES Application container failed to start with the following error and it causes Siebel server being started.
10-Sep-2021 14:10:44.154 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Error during ServletContainerInitializer processing
javax.servlet.ServletException: java.lang.NoSuchMethodException: org.glassfish.tyrus.server.TyrusServerConfiguration.<init>()
...
...
...
10-Sep-2021 14:10:44.156 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/siebel] startup failed due to previous errors
...
The behavior can be replicated at will with the following steps:
- Shutdown Siebel server and SES application container (tomcat server).
- Copy jar files from JMS vendor at <ses>/applicationcontainer_internal/lib
- Start SES application container.
Changes
The jar files from JMS vendor were located under <ses>/applicationcontainer_internal/lib for JMS settings.
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 |