Juan Velez opened SPR-12010 and commented

During a refresh() is possible that some beans may throw exceptions which causes the catch(BeanException) block to be executed. In this block the exception is not logged right away which may lead to the exception itself never being reported. Consider the case we encountered where we had (unfortunately) a deadlock situation which only happened once the code in the catch(BeanException) was being executed. The end result was that the system came to a stop and there was no report of any failure because the logging of the exception by spring only happens after the exception is re-thrown

Affects: 3.1.3, 4.0.6

Issue Links:

• Exception during context refresh swallowed by subsequent LifecycleProcessor exception handling [SPR-10000] #14634 Exception during context refresh swallowed by subsequent LifecycleProcessor exception handling
• Revisit BeansException warn logging after startup failure [SPR-13663] #18238 Revisit BeansException warn logging after startup failure

Backported to: 3.2.11