In my project, I am using Logback as logging facility. I have the following class
@Component
class Test {
@PreDestroy
public void destroy() {
try
To pick up Dovmo's answer. It's all about ordering. I have the same issue on Tomcat 8.5.x. Bacially, the initializer does an addListener
, you don't have any control over the listener. At shutdown, Tomcat reverse-iterates that list, picking the Logback listener first: Spring won't log anything.
A custom listener won't help because you cannot prepend it. What works for me on Tomcat is:
ch.qos.logback.classic.servlet.LogbackServletContextListener
org.springframework.web.context.ContextLoaderListener
logbackDisableServletContainerInitializer
true