cdm-server must not start instances with severe db connection problems
The cdm-server must not start instances with db connection problems.
Currently such instances show a unclear error message and status is reported as stopped
Error creating bean with name 'cdmVaadinConfiguration': Unsatisfied dependency expressed through field 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [eu/etaxonomy/cdm/security_base.xml]: Cannot resolve reference to bean 'hibernateProperties' while setting bean property 'hibernateProperties'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateProperties' defined in class path resource [eu/etaxonomy/cdm/opt/config/DataSourceConfigurer.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [java.util.Properties]: Factory method 'hibernateProperties' threw exception; nested exception is java.lang.NullPointerException
ref #9602 preventing instances from starting up in case of db connection problems