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

ZWE1SV Remains Up even with "Unable to start embedded Tomcat server" #2332

Open
dkelosky opened this issue Nov 13, 2024 · 3 comments
Open

ZWE1SV Remains Up even with "Unable to start embedded Tomcat server" #2332

dkelosky opened this issue Nov 13, 2024 · 3 comments
Labels
new question Further information is requested

Comments

@dkelosky
Copy link

I get a startup error Caused by: org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat server which followed a message ZWEAM510E Invalid key alias 'localhost'.

I needed to fix my zowe.yaml for the proper alias name; however, I noticed that the STC, ZWE1SV remains active even while services fail to start. Should Zowe services detect this scenario and shutdown automatically with a non-zero return code?

@dkelosky dkelosky added new question Further information is requested labels Nov 13, 2024
@balhar-jakub
Copy link
Member

Is the ZWE1SV general started task for the whole Zowe server, or is it a specific service? Also is the service being restarted? Because if yes, we already have somewhere issue to make sure zowe launcher doesn't restart failed services in certain cases that are unrecoverable.

@dkelosky
Copy link
Author

dkelosky commented Dec 3, 2024

Is the ZWE1SV general started task for the whole Zowe server

Yes. In my case though, I'm only starting API ML related services, e.g. discovery, gateway, catalog, and ZAAS I believe. Since this startup failure meant that nothing in the Zowe STC was usable, I expected everything to shutdown with an error.

@balhar-jakub
Copy link
Member

balhar-jakub commented Dec 4, 2024

The answer is yes as API ML squad we agree that in this situation the Zowe should stop altogether.

There is already a linked case in the Zowe Launcher - zowe/launcher#95

And other issue touching the problem in API Layer repository - zowe/api-layer#3518

With this stated the issue is related primarily to the Launcher and so I would expand on the issue above or move the issue there.

@balhar-jakub balhar-jakub transferred this issue from zowe/api-layer Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants