Users Unable to Log In to Heavily Loaded SGD Server, Error: "Fault String : (502)Bad Gateway"
(Doc ID 2527639.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.
The Administrator of a Secure Global Desktop (SGD) deployment running SGD 5.4 and the January 2019 maintenance patches receives reports that users are unable to authenticate with the SGD environment during peak usage time, with the following error message:
After receiving this report, the SGD Administrator found records of this response written to the Webservices logs (catalina.out) at the time of the outage:
Apr 05, 2019 10:01:11 AM org.apache.catalina.core.StandardWrapperValve invoke
INFO: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; The markup in the document preceding the root element must be well-formed.
parse: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; The markup in the document preceding the root element must be well-formed.
Under pressure, the SGD Administrator restarted SGD services on this node. This action resolved the report temporarily, but the behavior returned as the server returned to peak usage the following week.
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
|Tuning Secure Global Desktop|
|Managing High Production Loads with a SGD Array|
|Requesting Assistance for Deployment Tuning|