SGD 5.4 - Users Systematically Routed To Application Servers Where Login Script Timeout 
(Doc ID 2521685.1)
Last updated on JULY 08, 2019
Applies to:Oracle Secure Global Desktop - Version 5.4 and later
Information in this document applies to any platform.
After a long period of stability, the Administrator of a Secure Global Desktop (SGD) deployment configured for Application (Tier 3) load balancing received cascading reports of new application launch failures. A single instance of this behavior shortly morphed into reports that all new launch attempts of the load balanced application were failing.
In this scenario, existing user sessions were not impacted.
The catalyst for this event was found to be an unexpected delay in the SSH Authentication to the hosting application server. Though authentication was completing successfully in direct tests, the process was taking up to 3 minutes due to external variables native to that host. This delay was greater than the 'default' timers that are used to manage application launches on behalf of users in a SGD Deployment.
As the launch timer expired, SGD's launch scripts would consider the launch to have failed, and abort the attempt.
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