Update the CM1 service so that it detects when the database has gone down and stop the service instead of hanging and taking UI requests

Can CM1 service be stopped or not started when there is database failure or database connection issue?

It is very misleading now to show the running of CM1 service at service console without the successful connection of the core CM1 database.