I sometimes have the situation that when the tomcat is starting up, it could not connect to the database. May it be because the db is down (e.g. in a test system) or something other does not work out the way it should.
Unfortunately the entries in app.log show errors that happens as a consequence of that problem but are much later in the process. I then find myself in the situation of endless scrolling through the log file (either in the test systems or in studio itself).
One example of such a log file is posted here: https://www.cuba-platform.com/discuss/t/localhost-startstop-1-unable-to-update-sys_server-does-not-start
So I would like to know if it is possible to do some kind of application start preparation checks for the db (by the platform) and log this exact problem and then stop the tomcat startup process (if this is possible). This way the error messages in the logs regarding the startup process become more clear.
What do you think about that?