After Siebel Enterprise Restart Accessing The Any Siebel Application Results In "Server Busy" Error In The Browser and "404" Errors in Tomcat Log Files
(Doc ID 2963337.1)
Last updated on JULY 25, 2023
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
When attempting to access the Siebel URL, the following error occurs:
Environment was set up over 3 nodes , with a Gateway Cluster on all of them and Siebel Server running on 2 of them.
Steps:
- Start Siebel 22.10 Application as per bookshelf instructions:
https://docs.oracle.com/cd/F26413_34/books/SystAdm/c-Starting-a-Siebel-CRM-Deployment-ad1181012.html#ad1181012 - Wait for all the services to be up and running
- Attempt to access the Siebel application via either load balancer or direct AI connection
https://<AI_HOST>:<AI_HTTPS_PORT>/siebel/app/<application_name>/<lang>
Changes
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 |