Oracle Traffic Director Health Check Doesn't Trigger After Getting 503 From Origin Server
Last updated on JUNE 20, 2017
Applies to:Oracle Traffic Director - Version 220.127.116.11.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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms