search cancel

ZWES1606W Failed to get JWK

book

Article ID: 258020

calendar_today

Updated On:

Products

Brightside

Issue/Introduction

Found multiple ZWES1606W warning messages in the ZOWE STC, can those messages can be ignored ?

 2023-01-03 18:12:54.519 <ZWEADS1:main:33554950> ZWESVUSR INFO  (o.z.a.p.s.ServiceStartupEventHandler) ZWEAM000I Discovery Service started in 70.161 seconds
 error initing session: 6
 failed to obtain JWK, status = 9
 ZWES1606W Failed to get JWK - failed to send HTTP request, retry in 10 seconds
 HTTP status 404
 failed to obtain JWK, status = 2
 ZWES1606W Failed to get JWK - HTTP response error, retry in 10 seconds
 HTTP status 404
 failed to obtain JWK, status = 2
 ZWES1606W Failed to get JWK - HTTP response error, retry in 10 seconds
 HTTP status 404
 failed to obtain JWK, status = 2
 ZWES1606W Failed to get JWK - HTTP response error, retry in 10 seconds
 HTTP status 404
 failed to obtain JWK, status = 2
 ZWES1606W Failed to get JWK - HTTP response error, retry in 10 seconds
 2023-01-03 18:13:36.355 <ZWEAGW1:DiscoveryClient-CacheRefreshExecutor-0:33555192> ZWESVUSR WARN  (o.z.a.g.s.s.z.ZosmfService) The check of z/OSMF JWT builder endpoint has failed
 HTTP status 404
 failed to obtain JWK, status = 2
 ZWES1606W Failed to get JWK - HTTP response error, retry in 10 seconds
 2023-01-03 18:13:47.407 <ZWEAAC1:DiscoveryClient-CacheRefreshExecutor-0:33555249> ZWESVUSR WARN  (o.z.a.a.s.c.CachedProductFamilyService) ZWEAC705W The home page url for service ZSS was not transformed. Not able to select route for url https://199.214.72.11:7557/ of the service zss. Original url used.
 2023-01-03 18:13:47.413 <ZWEAAC1:DiscoveryClient-CacheRefreshExecutor-0:33555249> ZWESVUSR WARN  (o.z.a.a.s.c.CachedProductFamilyService) ZWEAC705W The home page url for service IBMZOSMF was not transformed. Not able to select route for url https://199.214.72.11:443/ of the service ibmzosmf. Original url used.
ZWES1601I Server is ready to accept JWT with fallback to legacy tokens

 

Environment

Release : 2.0

ZOWE 2.4.0

Resolution

ZOWE server contains mutiple components, As all the components are coming online at the same time, mutiple attempts to obtain JWT (with ZWES1606W warning) can be found in the STC log in case component comes up before the component providing the JWT. 

Those warning messages can be ignored If the component eventually obtianed JWT token successfully - check the following message in ZOWE STC log after multiple ZWES1606W messages

  • ZWES1601I Server is ready to accept JWT with fallback to legacy tokens