My Oracle Support Banner

OHS 11.1.1.7.0 Does Not Recover from DNS Outage and Errors with "badSrvr: Can't locate Server with host" (Doc ID 2424819.1)

Last updated on MAY 08, 2020

Applies to:

Oracle HTTP Server - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

OHS + mod_wl_ohs , does not re-establish connection against WLS servers after a networking outage.

After a full network outage (lack of connectivity against all services, including dns down), the HTTPD process does not handle properly the re-connection against the WLS servers.

The mod_wl_ohs plugin logs, the following errors can be seen

2018-05-30T14:15:06.0987+02:00 parseServerList: could not resolve hostname '<HOSTNAME>', treating it as invalid, error [670003] Temporary failure in name resolution
2018-05-30T14:15:06.0988+02:00 parseServerList: could not resolve hostname '<HOSTNAME>', Unable to create connection to server
2018-05-30T14:15:06.0988+02:00 parseServerList: could not resolve any valid WLS hostname specified in the static list
2018-05-30T14:15:06.0988+02:00 badSrvr: Can't locate Server with host '~P▒^C ▒^?' port 0 useSSL 0
2018-05-30T14:15:11.1012+02:00 *******Exception type [NO_RESOURCES] (apr_sockaddr_info_get call failed with error=670002 ) raised at line 1602 of URL.cpp
2018-05-30T14:15:11.1013+02:00 badSrvr: Can't locate Server with host ' ▒^CL▒^?' port 0 useSSL 0 
2018-05-30T14:15:11.1012+02:00 *******Exception type [NO_RESOURCES] (apr_sockaddr_info_get call failed with error=670002 ) raised at line 1602 of URL.cpp
2018-05-30T14:15:11.1013+02:00 badSrvr: Can't locate Server with host ' ▒^CL▒^?' port 0 useSSL 0
2018-05-30T14:15:16.0992+02:00 request [/<URI1>/app_status.html] did NOT process successfully..................
2018-05-30T14:15:17.1015+02:00 request [/<URI2>/app_status.html] did NOT process successfully..................


And after that point .. even if WLS applications were accessible directly .. the OHS instances did not recover and reported errors

2018-05-30T14:15:30.5485+02:00 request [/<URI1>/app_status.html] did NOT process successfully.................. 
2018-05-30T14:15:31.4503+02:00 request [/<URI2>/app_status.html] did NOT process successfully.................. 
This lasted until OHS got restarted.

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.