You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.
I've got a Spring application (not Spring Boot) where I've integrated logback-extensions in order to programatically configure appenders. For example, the console appender is only configured for the "dev" profile (as per the logback-extensions wiki page using a DelegatingLogbackAppender).
This works great except the case where there is an error during context initialization. Then, Spring seems to destroy the delegated appender before the final error message gets logged! (e.g. "ERROR org.springframework.web.context.ContextLoader - Context initialization failed" followed by a stack trace).
Is there any way to work around this limitation and somehow delay the destruction of this appender?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've got a Spring application (not Spring Boot) where I've integrated logback-extensions in order to programatically configure appenders. For example, the console appender is only configured for the "dev" profile (as per the logback-extensions wiki page using a DelegatingLogbackAppender).
This works great except the case where there is an error during context initialization. Then, Spring seems to destroy the delegated appender before the final error message gets logged! (e.g. "ERROR org.springframework.web.context.ContextLoader - Context initialization failed" followed by a stack trace).
Is there any way to work around this limitation and somehow delay the destruction of this appender?
The text was updated successfully, but these errors were encountered: