Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java processes keep running after Zowe job is stopped #95

Open
arxioly opened this issue Aug 8, 2023 · 2 comments
Open

Java processes keep running after Zowe job is stopped #95

arxioly opened this issue Aug 8, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@arxioly
Copy link

arxioly commented Aug 8, 2023

APIML java processes are still working after graceful (using /P) shutdown of Zowe.

Steps to reproduce:

  1. Start Zowe using /S
  2. Wait for the API Catalog to be available
  3. Stop Zowe using /P
  4. Check for runnning java processes under Zowe user in USS by issuing following command:
ps -ef | grep java

Expected result:
Zowe Launcher stopped all Zowe processes.

Zowe version: 2.9.0

The logs from shutdown:

2023-08-08 10:59:37 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0014I termination command received
2023-08-08 10:59:37 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0015I console listener stopped
2023-08-08 10:59:37 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0008I stopping components
CEE5205S The signal SIGTERM was received.
2023-08-08 09:05:51 <ZWELS:50397341> ZWESVUSR INFO (zwe-internal-start-component) starting component gateway ...
CEE5205S The signal SIGTERM was received.
2023-08-08 09:05:49 <ZWELS:83951759> ZWESVUSR INFO (zwe-internal-start-component) starting component api-catalog ...
CEE5205S The signal SIGTERM was received.
2023-08-08 09:05:50 <ZWELS:50397305> ZWESVUSR INFO (zwe-internal-start-component) starting component discovery ...
2023-08-08 10:59:40 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0004I component gateway(67174550) terminated, status = 36608
2023-08-08 10:59:40 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0002I component gateway stopped
2023-08-08 10:59:40 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0004I component api-catalog(16842944) terminated, status = 36608
2023-08-08 10:59:40 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0002I component api-catalog stopped
2023-08-08 10:59:41 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0004I component discovery(33620027) terminated, status = 36608
2023-08-08 10:59:41 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0002I component discovery stopped
2023-08-08 10:59:41 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0009I components stopped
2023-08-08 10:59:41 <ZWELNCH:83951752> ZWESVUSR INFO ZWEL0022I Zowe Launcher stopped
@arxioly arxioly added the bug Something isn't working label Aug 8, 2023
@1000TurquoisePogs
Copy link
Member

@1000TurquoisePogs @struga0258 we can reproduce this if you need @ifakhrutdinov ... I can reproduce java code staying around after zowe dies even in the absense of the launcher (when, in development, sometimes i run zwe directly under USS and manage the processes myself)

@ifakhrutdinov
Copy link
Contributor

@arxioly can you please upload the full logs of the launcher and the affected Java components? Ideally in cases when this happens and doesn't happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants