Siebel Object Manager Hangs in "Handling Logon" or "Cleaning Up" Status and Several Users Cannot Login to the Application - HTTP 500 and Server is Busy Errors Are Observed
(Doc ID 2777213.1)
Last updated on MAY 17, 2021
Applies to:Siebel CRM - Version 20.6 and later
Information in this document applies to any platform.
At times it is possible to observe several Siebel object manager component tasks hanging in "Handling Logon" or "Cleaning Up" status without progress.
As the number of tasks in "Handling Logon" or "Cleaning Up" status increases it is also observed an increase on the number of busy threads on the Apache Tomcat JVM for Siebel Application Interface.
The end users may receive a generic HTTP 500 or "Server is Busy..." error on the browser window.
The end users try to re-login by closing the browser window and retrying, but the Siebel application does not respond and several users are impacted at the same time.
The issue can be reproduced at will with the following steps:
1. Try to login to the application, it may not respond immediately
2. The generic HTTP 500 or "Server is busy..." error may be returned after a little while
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