Oracle Traffic Director Health Check Doesn't Trigger After Getting 503 From Origin Server
(Doc ID 2141242.1)
Last updated on JUNE 20, 2017
Applies to:Oracle Traffic Director - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
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, QAsys01 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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!