JCLCheck REST API log shows Broadcom DNS name
Article ID: 437289
Updated On:
Products
Issue/Introduction
The REST API fails to start. Why does Broadcom DNS name (example.broadcom.net) show up in the JCLCheck REST API log?
Sample message where the DNS name is found when using the REST API v2.0.2 and older:
-yyy-mm-dd hh:mm:sssss WARN 67113947 --- [ main] c.n.d.s.t.d.RetryableEurekaHttpClient : Request execution failed with
message: java.net.UnknownHostException: example.broadcom.net: example.broadcom.net: EDC9501I The name does not resolve
for the supplied parameters.
or for REST API v2.0.3:
Error creating bean with name 'apimlRegistrator': Injection of autowired dependencies failed; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'IP_32' in value "${IP_32}"
Cause
The user is missing an "apiml" section in the jclcheck.yml so the internal default values are picked up instead.
These internal defaults—including system references like example.broadcom.net or symbols like IP_32 —are intended for our environment rather than for end users.
Note the following changes between versions:
- REST API version 2.0.2 and earlier: The compiled binary application.yml file contains direct references to our systems (e.g., example.broadcom.net).
- REST API version 2.0.3 and higher: The compiled binary application.yml contains symbols, such as IP_32.
Resolution
Provide a default apiml section in the jclcheck.yml file as follows:
apiml:
enabled: false
service:
hostname: my.host.name
serviceIpAddress: 1.1.1.1
Once the REST API is successfully running, then valid apiml values should be set and apiml may be turned on (enabled: true) in the jclcheck.yml.
Note: API ML is not required to use the JCLCheck REST API. Enabling API ML to add services such as discovery, catalog, load-balancing/failover, SSO, etc.
Feedback
