Oracle Traffic Director (OTD) Fails To Connect to Origin Server in SOA Cloud Service (SOACS)

(Doc ID 2299318.1)

Last updated on AUGUST 24, 2017

Applies to:

SOA Suite Cloud Service - Version N/A and later
Oracle Traffic Director - Version and later
Information in this document applies to any platform.


The steps at are followed to add a Load Balancer (running OTD) to an newly created SOACS instance prod_inst. This setup is working properly when accessing the SOACS instance via the OTD added from Oracle SOA Cloud Service Console.

Then another SOACS instance is created and let's call a qa_inst. The OTD created from above is re-configured to add a route to this qa_inst SOACS instance. After restarting the OTD, testing shows that the OTD fails to send requests destined to qa_inst instance. However the requests destined to the prod_inst are processed successfully.

The OTD log shows the origin servers in the qa_inst SOACS instance is unreachable:

[2017-05-04T02:05:25+00:00] [otd_opc-config_soupcsprod-ncr-jcs-lb-1] [TRACE:32] [OTD-10962] [health-check] [pid: 30033] trying to OPTIONS /, check-http-server reports: server soupcscert-jcs-wls-1:9073 server unreachable
[2017-05-04T02:05:25+00:00] [otd_opc-config_soupcsprod-ncr-jcs-lb-1] [WARNING:1] [OTD-11016] [health-check] [pid: 30033] , health-check reports: all servers in origin server pool osp-CERT-CS are offline.

The ping command is also used to verifiy network connectivity from the OTD VM to the qa_inst VM but it also fails. curl and wget issued from the OTD system are also unable to fetch content from qa_inst SOACS instance.




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