- configuration errors on startup are no longer collected in the 'errors' attribute, but logged immediately and counted in a new 'logError' method. - generalConfig may be configured to raise the errors immediately instead - Raise immediately on unhandled errors. Some of them were catched before which may lead to strange follow up errors. - do not start poller thread, when the error count is non-zero - as before, simple connection failures are not preventing startup, but now more severe errors (bad uri) will stop the server Change-Id: I4f84ee8e86cf2925108c0fe92eaab796bb731091 Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/37776 Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de> Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>
31 KiB
31 KiB