Closed hvisage closed 6 years ago
The upcoming 7.2 release, (which I still have to finish up) now also exposes the timeout argument for the start_runtime api call (see develop branch). Thanks for pointing it out. I added a lot of them recently, to be able to actually set timeouts, but this one was still missing.
Also notice that the different levels of granularity of runtime api calls cause a different amount of feedback / progress report that we can get from the Mendix Runtime.
The whole start procedure is already divided into a number of steps, but each individual one just blocks until it's done or reports an error. Progress is logged to the application log file, but there's no way for the caller to find out if it's trying to connect the database, running the after-startup microflow etc.
Included in v7.2-rc1
Goodday,
so, busy with Ansible deploys, and I have errors with database connectivity, which causes the
m2ee start
to hang indefinitely.The errors that scrolls through the log file:
Yes, I also have a 2nd JDBC connection (where the Mendix App in this case fetches data to populate the "main"/modeller database).
What I'm in need of, is a sorta time-out for the start to fail with some errors if the Mendix doesn't start up in time. This might be to consider in the light of things like model (database structure) changes that does take a long(er) time to complete...