You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An API ML (ZWE*) message should rather be logged, with information about what actions the user should take:
i.e. Authentication service is not registered. Please verify the configuration and whether it is available
The status response 503 indicating that the service is DOWN should also returned.
The text was updated successfully, but these errors were encountered:
taban03
added
bug
Verified defect in functionality
new
New issue that has not been worked on yet
labels
Jun 5, 2024
taban03
changed the title
Remove system.exit from the health indicator
Remove system.exit from the health indicator and enhance the exception handler
Jun 5, 2024
The addition of the log message with the correct message ID seems to be the correct direction.
As for the removal of System.exit - The authentication service doesn't exist or isn't working and as such the API Mediation Layer wouldn't work, stopping it seems like a reasonable choice. Can we use other way to stop it?
The addition of the log message with the correct message ID seems to be the correct direction.
As for the removal of System.exit - The authentication service doesn't exist or isn't working and as such the API Mediation Layer wouldn't work, stopping it seems like a reasonable choice. Can we use other way to stop it?
I think the problem is that stopping it triggers a restart of the service by launcher. We've discussed this in the past, we should have a way to stop it without triggering a restart.
In this particular case it may require a user action to fix connection with z/OSMF.
I was thinking about the scenario with SAF provider, in this case the z/OSMF part of the condition will also not trigger.
Describe the bug
The health indicator class contains system.exit, that shouldn't be used, in favour of unhealthy response
An API ML (ZWE*) message should rather be logged, with information about what actions the user should take:
i.e.
Authentication service is not registered. Please verify the configuration and whether it is available
The status response 503 indicating that the service is DOWN should also returned.
https://github.com/zowe/api-layer/wiki/Issue-management
The text was updated successfully, but these errors were encountered: