Caching Service Binding Hostname Is Unresolvable
Last updated on MARCH 19, 2017
Applies to:Application Container Cloud - Version N/A to N/A
Information in this document applies to any platform.
On : 17.1.3 version, Node Cloud Service
A cache is configured according to the documentation in "Using Caches in Oracle Application Container Cloud Service". A new Node.js application is created with a service binding to the created cache. The node application obtains the cache hostname from the CACHING_INTERNAL_CACHE_URL environment variable. The caching URL is assembled as follows:
An ENOTFOUND failure on getaddrinfo implies that the hostname lookup is failing.
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