The Gateway says that is shutdowning but nothing happened
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
During the implementation of https://github.com/zowe/api-layer/pull/3068/files#diff-0e175ceba3da781027d950f2e3942b4738b68a121f7d9faf4880a968a5f99f0f there was remove System.exit (https://github.com/zowe/api-layer/blob/c8a23a88c041b0db9455bad89cf5061b84473ce5/gateway-service/src/main/java/org/zowe/apiml/gateway/security/service/JwtSecurity.java#L274). Even this is it aim to remove system exit calls (https://github.com/zowe/api-layer/issues/2941), now the behavior could be strange.
The gateway writes the message z/OSMF instance '%s' not found or incorrectly configured. Gateway is shutting down. but the service is still alive.
How to simulate:
- start DS, GW, and mock service (mock service with a communication issue - ie unsupported TLS)
- wait 5mins
- The log contains multiple error messages, but GW is still running
Expected behavior:
The Gateway is stopped
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in gateway-service and inspect the JwtSecurity.java shutdown path referenced by the issue and PR 3068. Reproduce the unsupported-TLS mock-service scenario by starting DS, GW, and the mock service, then waiting five minutes while checking the logs. Done means the Gateway stops instead of remaining alive after reporting that the z/OSMF instance was not found or incorrectly configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100