Oracle Traffic Director Health Check does not Trigger after Getting 503 from Origin Server
(Doc ID 2141242.1)
Last updated on SEPTEMBER 22, 2023
Applies to:
Oracle Traffic Director - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Symptoms
OTD is configured to use HTTP GET with <response-code-match> of 200 for health checking.
Below shows an excerpt of the server.xml file:
After that, <HOSTNAME1> starts sending 503 again that OTD is no longer able to detect.
The logs shows no health check probes being sent out.
Health check just stopped.
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 |
Cause |
Solution |
References |