#16626 added warn logging to AbstractApplicationContext to ensure that BeansExceptions don't get missed.
Although the intention is good, it has the unwanted side effect of causing most refresh failures to log stacktraces twice. This is particularly obvious with Spring Boot applications where a simple startup failure results in multiple stack-traces.
We could provide a feature flag to suppress the message.
I'm in two minds about the feature flag. We could probably argue that warn logging is overkill and simply downgrade it to debug. The message was only added because the original reporter of #16626 had a deadlock, for most situations the rethrown exception will be logged eventually.