Siebel IP2017: New session cannot be created at component level after process restart
(Doc ID 2787332.1)
Last updated on JUNE 29, 2021
Applies to:Siebel CRM - Version 20.6 and later
Information in this document applies to any platform.
Siebel Application Object Manager is not accessible for end users and "server busy" message is shown in browser.
When this situation occurs, all subsequent logins for that Siebel component will fail and the request for discovery string returns HTTP 500 error (see localhost_access_log*.txt from Cloud Gateway):
This kind of behavior is observed in case of Siebel environments that are impacted by excessive number of crashes or component restarts (for example, over 100 crashes / process restarts per day for each individual Siebel component).
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