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

[BUG] handles the program if the database is down ("service unavailable") #53

Open
JekxDevil opened this issue Dec 11, 2022 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@JekxDevil
Copy link
Contributor

Describe the bug
When we start the server and there is no database attached, or even when the latter goes down afterwards, the moment the back-end needs to provide a result using a query to ask to the database, the error throw by the fact that mongodb is down is not catch and make all the program crash.
Would be nice to catch it and redirect to a front-end dedicated page stating that the service is currently unavailable.
And redirect the user to the previous page (in M2, the login is the only one supported due to authorization) whenever the db connection becomes available again.

To Reproduce
Steps to reproduce the behavior:

  1. Don't initialize the db service
  2. Start the handshake server
  3. See error

Expected behavior
Server crash. Error level: HIGH

Screenshots
none

Desktop:

  • OS: Ubuntu 22.04 LTS
  • Browser: Chromium
  • Version: 108.0.5359.94 snap
@JekxDevil JekxDevil added the bug Something isn't working label Dec 11, 2022
@cosmcif cosmcif added this to the Milestone 4 milestone Dec 12, 2022
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

4 participants