Errors detected when we try to start Zowe 2.5.

[dsegoviaMF]

When we try to start our instance of Zowe 2.5 we find the next errors:

2023-04-03 12:00:50.537 ZWEAGW1:Thread-14:84017635 IZUSVR ERROR (o.z.a.g.s.s.JwtSecurity) ZWEAG713E Configuration error when trying to establish JWT producer. Events: Wait for zOSMF to come online before deciding who provides JWT tokens. Started waiting for zOSMF to be registered and known by the discovery service
2023-04-03 12:00:50.538 ZWEAGW1:Thread-14:84017635 IZUSVR ERROR (o.z.a.g.s.s.JwtSecurity) ZWEAG108E z/OSMF instance 'zOSMF' not found or incorrectly configured. Gateway is shutting down.
2023-04-03 12:00:51.315 ZWEAGW1:SpringApplicationShutdownHook:84017635 IZUSVR WARN (o.s.c.a.CommonAnnotationBeanPostProcessor) Destroy method on bean with name 'webSocketClientFactory' threw an exception: java.util.regex.PatternSyntaxException: Stack overflow during pattern compilation near index 1.*Error during filtering.Token is not valid.
¬
2023-04-03 12:01:01 ZWELNCH:131865 IZUSVR INFO ZWEL0004I component gateway(33686298) terminated, status = 0
2023-04-03 12:01:01 ZWELNCH:131865 IZUSVR ERROR ZWEL0038E failed to restart component gateway, max retries reached

We check that our zosmf is running without errors.

Anybody knows if there is some new parameter in zowe 2.5 relationated with zOSMF or which parameters we need to check to try the resolver our problem?

[zFernand0]

I believe that the @zowe/api-mediation-administrators team might be able to help here 😋

---

Here is the corresponding APIML issue:

• Errors detected when we try to start Zowe 2.5. api-layer#2874

[pinpan]

It looks like a misconfiguration issue indeed. A close inspection of the config may resolve it quickly.

Explanation:
The issue happens when zOSMF is configured as a JWT provider in the APIML GW and the GW security checks for zOSMF availability fail.

The check is done repeatedly for a preconfigured number of times and a time interval. After that, if the validation is not successful GW concludes that zOSMF is not available and shuts down.

The validation check is based on zOSMF service ID and end-point URI. If the ID is wrong zOSMF wouldn't be found as a service registered in Eureka, hence it is supposed to be not available. If it is found to be available, the endpoint is tried to check if zOSMF is online.

From the log above it is not clear which condition is not satisfied. Debug level of logging would be helpful here.