fix: Fix detection of connection issue

[pj892031]

Description

This PR fixes a potential NullPointerException when Eureka checks if the communication was broken because of network:

2025-05-29 12:34:42.714 <ZWEADS1:TaskBatchingWorker-target_XXXXX-0:17105739> �[35mZWESVUSR�[0;39m �[36mWARN �[0;39m ((c.n.e.u.b.TaskExecutors)) Discarding 4 tasks of TaskBatchingWorker-target_XXXXX-0 due to permanent error
2025-05-29 12:34:50.769 <ZWED:33883042> ZWESVUSR CRITICAL (_zsf.apiml,EurekaClient.js:703) Problem making eureka request Error: connect ECONNREFUSED [10.175.84.32:XXXXX](http://XXXXX:XXXXX/)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
  errno: -1128,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '10.175.84.32',
  port: XXXXX
}
2025-05-29 12:34:50.770 <ZWED:33883042> ZWESVUSR WARN (_zsf.apiml,EurekaClient.js:710) Eureka request failed to endpoint https://XXXXX:XXXXX/eureka/apps, next server retry in 10000ms
2025-05-29 12:35:04.095 <ZWEAGW1:parallel-2:17107183> �[35mZWESVUSR�[0;39m �[36mERROR�[0;39m ((o.z.a.p.v.BuildInfo)) ZWEAM100E Could not read properties from: 'META-INF/git.properties'
2025-05-29 12:36:41.253 <ZWEADS1:TaskBatchingWorker-target_XXXXX-0:17105739> �[35mZWESVUSR�[0;39m �[36mWARN �[0;39m ((o.z.a.p.e.c.ApimlPeerEurekaNode)) APICATALOG/XXXXX:apicatalog:XXXXX:Heartbeat@XXXXX: missing entry.
2025-05-29 12:36:41.260 <ZWEADS1:TaskBatchingWorker-target_XXXXX-0:17105739> �[35mZWESVUSR�[0;39m �[36mWARN �[0;39m ((o.z.a.p.e.c.ApimlPeerEurekaNode)) APICATALOG/XXXXX:XXXXX:Heartbeat@XXXXX: cannot find instance id XXXXX:apicatalog:XXXXXand hence replicating the instance with status UP
2025-05-29 12:49:25.048 <ZWEAAC1:scheduling-1:17105717> �[35mZWESVUSR�[0;39m �[36mERROR�[0;39m ((o.z.a.a.s.c.CachedProductFamilyService)) ZWEAC708E The API base path for service IDMS-API-SERVICE was not retrieved. Not able to select API base path for the service idms-api-service. Original url used.
2025-05-29 13:00:53.149 <ZWEAAC1:https-jsse-nio-0.0.0.0-XXXXX-exec-3:17105717> �[35mZWESVUSR�[0;39m �[36mWARN �[0;39m ((o.s.w.s.m.s.DefaultHandlerExceptionResolver)) Resolved [org.springframework.web.context.request.async.AsyncRequestNotUsableException: ServletOutputStream failed to write: java.io.IOException: EDC5140I Broken pipe. (errno2=0x76697242)]
2025-05-29 13:39:58.445 <ZWEADS1:TaskBatchingWorker-target_XXXXX-1:17105739> �[35mZWESVUSR�[0;39m �[36mERROR�[0;39m ((javax.net.ssl)) Fatal (HANDSHAKE_FAILURE): Couldnt kickstart handshaking
2025-05-29 13:40:48.911 <ZWEAGW1:DiscoveryClient-CacheRefreshExecutor-%d:17107183> �[35mZWESVUSR�[0;39m �[36mERROR�[0;39m ((javax.net.ssl)) Fatal (UNEXPECTED_MESSAGE): Connection reset
2025-05-29 13:40:54.903 <ZWEAAC1:scheduling-1:17105717> �[35mZWESVUSR�[0;39m �[36mERROR�[0;39m ((javax.net.ssl)) Fatal (UNEXPECTED_MESSAGE): EDC5140I Broken pipe. (errno2=0x76697242)
2025-05-29 13:39:58.444 <ZWEADS1:TaskBatchingWorker-target_XXXXX-0:17105739> �[35mZWESVUSR�[0;39m �[36mWARN �[0;39m ((c.n.e.u.b.TaskExecutors)) Discovery WorkerThread error
java.lang.NullPointerException: Cannot invoke "java.lang.String.toLowerCase()" because the return value of "java.lang.Throwable.getMessage()" is null
    at org.zowe.apiml.product.eureka.client.ApimlPeerEurekaNode$ReplicationTaskProcessor.maybeReadTimeOut(ApimlPeerEurekaNode.java:581)
    at org.zowe.apiml.product.eureka.client.ApimlPeerEurekaNode$ReplicationTaskProcessor.process(ApimlPeerEurekaNode.java:480)
    at com.netflix.eureka.util.batcher.TaskExecutors$BatchWorkerRunnable.run(TaskExecutors.java:178)
    at java.base/java.lang.Thread.run(Thread.java:857)
2025-05-29 13:40:55.865 <ZWEAGW1:DiscoveryClient-CacheRefreshExecutor-%d:17107183> �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.a.h.c.h.i.c.HttpRequestRetryExec)) Recoverable I/O exception (java.net.SocketException) caught when processing request to {s}->[https://XXXXX:XXXXX/]

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
84.2% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud