Bugs related to MongoDB going down in back-end

[Christoffer-Cortes]

Description

• When mongodb goes down it takes 1m of timeout before you get the 500 response.
  If the page is refreshed however it will get the Back-end status is unknown warning until it gets 500 after 1m.
  This status is not shown if the page is not refreshed and back-end goes from being up to down.
  There needs to be better feedback when mongodb is down or better standardized message.
  Preferably this feedback could be given quicker than a 1m delay.

• If you try to add a subscription while the mongodb is down the save button will say 'Saving...' and get stuck like this without any error message to the user. This is sort of the same problem as above, the timeout for the request is 1m and the user needs some sort of quick feedback that something is wrong.

• This error is not related to the mongodb issues but I'm letting it piggyback.
  If ldap.enabled is set to true front-end will disable subscription CRUD buttons.
  If you remain in the page and bring back-end down and bring it back up again with ldap.enabled false, then CRUD buttons will still be disabled.
  These buttons need to be refreshed when the status changes.

Motivation

Less unwanted behavior in the GUI.

Exemplification

Benefits

The quicker feedback to the user I believe would be appreciated.

Possible Drawbacks

This may be due to seldom update and check of back-end status. A change in back-end has been made to update status more frequently. The status check could as well be reduced but may lead to more trafic towards back-end just to check status. Investigate if the problem has been reduced.