Raise log level when bean destruction fails

[boojongmin]

related to this issue #23199

logger runned on org.springframework.beans.factory.support package.
but InvocationTargetException was makes by my code.
I want to check my error log.

[jhoeller]

On review, this is a regression from 5.0/4.3 where we mostly logged bean destruction exceptions at warn level. Restoring this in 5.1.9 seems feasible, even within the revised log level usage that we introduced in 5.1 (for less noise at info and warn level). That said, such exceptions are technically not a hard error but rather just a partial effect in a multi-step destruction process, so logging at error level would arguably create unnecessary (follow-up) noise for scenarios with many related beans that need to be destroyed. This is particularly relevant for production scenarios where error level may trigger operator escalations.

Generally speaking, we recommend running with info or at least warn log level in development. Also, destroy method ideally should not propagate exceptions but rather handle them locally (possibly even log them locally with a descriptive log message).

[boojongmin]

@jhoeller

Thank you for your kind reply.
Kotlin handles errors with an unchecked exception.
My mistake is that when I close a resource like db, I miss the try-catch block related to checked exception like Java. I think kotlin programmer might have experience like me when I close resources.
Thank you.