Is it possible to dynamically restart API ML components (gateway, catalog, discovery)?

[PavelKondratiev]

See title, thanks in advance for response!

[balhar-jakub]

It would be great to understand a bit more about what you are trying to do and how do you start Zowe. Do you use zwe start command or do you start it via /S ZWESLSTC or do you use some other way. Also what dynamically means for you.

In general if you start zowe via zwe start this actually starts launcher that spawns subtasks for each of these servers. As such if you kill the related job, the zowe launcher starts it again. Is this what you were looking for?

[balhar-jakub]

And the specific commands to actually stop and start Zowe should be:
/F ZWESLAML,APPL=STOP(gateway)
/F ZWESLAML,APPL=START(gateway)

[PavelKondratiev]

Hi Jakub,

Thanks for the prompt response.
I use Zowe version 1.27 on zPDT, start it by /S ZWESVSTC command.
The reason of question is my gateway subtask constantly shuts down as follows :

2024-06-10 19:13:16.910 ZWEAGW1:main:33620623 ZWESVUSR INFO (o.z.a.p.s.ServiceStartupEventHandler) ZWEAM000I Gateway Service started in 5330.488 seconds
2024-06-10 21:03:17.201 ZWEAGW1:Thread-17:33620623 ZWESVUSR 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 t
Started waiting for zOSMF to be registered and known by the discovery service

... lots of messages " Discovery Service Cache was updated."

2024-06-10 21:03:17.227 ZWEAGW1:Thread-17:33620623 ZWESVUSR ERROR (o.z.a.g.s.s.JwtSecurity) ZWEAG108E z/OSMF instance 'zOSMF' not found or incorrectly configured. Gateway is shutting down.
2024-06-10 21:03:36.525 ZWEAGW1:SpringContextShutdownHook:33620623 ZWESVUSR WARN (o.s.c.a.CommonAnnotationBeanPostProcessor) Destroy method on bean with name 'webSocketClientFactory' threw an exception: java.util.regex.PatternSyntax
.*Error during filtering.Token is not valid.

So afterwards I see only ZWE1AC and ZWE1AD subtasks are active and ZWE1AG is not.
zOSMF itself is up and reachable via web interface.

I tried /F ZWESVSTC,APPL=START(gateway) you suggested and got message "IEE342I MODIFY REJECTED-TASK BUSY"
Gratefully appreciate any suggestions about recovering gateway subtask without restarting main STC - thanks!

[balhar-jakub]

The guidance would be valid for V2, For V1 I will validate the correct solution.

Do you have any plans to move to the V2.x of Zowe?

[PavelKondratiev]

Not at the moment, we got V1 preinstalled within ADCD

[codezfire]

It appears the gateway has shut down due to errors or configuration issues.
You can enable debug mode for Zowe to identify the problems.
Restarting the gateway alone won't resolve the issue without addressing the underlying cause.

I don't think it's possible to start individual components dynamically.
Any changes to the YAML configuration will require a restart of the Zowe server STC.

We recommend upgrading to Zowe V2, as it offers easier installation, usage, and faster startup.
Additionally, you can use HA mode for load balancing and maintenance without downtime.
Let us know if you need assistance upgrading to zowe V2 or V3 in the future.

[PavelKondratiev]

Many thanks for the responses, closing discussion