Resolving timeout problems in z/OSMF authentication services
search cancel

Resolving timeout problems in z/OSMF authentication services


Article ID: 276798


Updated On:




Generating JWT from zowe API mediation layer via z/OSMF failed in timeout.

Below is the error seen in zowe started task log:

YYYY-MM-DD HH:MM:SS.sss <xxxxxxxx:ThreadPoolTaskExecutor-1:########> xxxxxxxx ERROR (o.z.a.d.GatewayNotifier) ZWEAD400E Cannot notify Gateway on '' about new instance ''

YYYY-MM-DD HH:MM:SS.sss <xxxxxxxx:ThreadPoolTaskExecutor-1:########> xxxxxxxx ERROR (o.z.a.d.GatewayNotifier) ZWEAD704E Gateway Service is not available so it cannot be notified about changes in Discovery Service

YYYY-MM-DD HH:MM:SS.sss <xxxxxxxx:https-jsse-nio-> xxxxxxxx ERROR (o.z.a.g.s.s.z.ZosmfService) ZWEAG104E Authentication service is not available at URL 'https://zosmf-xxx.xx.xx:xxx/zosmf/services/authenticate'. Error returned: 'I/O error on POST request for &quot;https://zosmf-xxx.xx.xx:xxx/zosmf/services/authenticate&quot;: Read timed out; nested exception is Read timed out'

YYYY-MM-DD HH:MM:SS.sss <xxxxxxxx:https-jsse-nio-> xxxxxxxx ERROR (o.a.c.c.C.[.[.[.[dispatcherServlet]) Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception Could not get an access to z/OSMF service.


What might cause the timeout and is there available parameter to adjust in order to increase timeout value ?


To increase the timeout, update zowe.yaml file with these 2 environmental variables.

Their values are in milliseconds, in the sample below 40 seconds are requested.


Additional Information

Documentation about how to add these variables(UPPER_CASE format as provided is authorized) can be found on Zowe docs website