jboss关闭未发生,停留在消息:关闭Spring根WebApplicationContext [英] jboss shutdown not happening, stuck at message: Closing Spring root WebApplicationContext

查看:83
本文介绍了jboss关闭未发生,停留在消息:关闭Spring根WebApplicationContext的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

2010-01-30 03:25:27,598信息[org.apache.catalina.core.ContainerBase]关闭Spring FrameworkServlet'expertx'的WebApplicationContext 2010-01-30 03:25:27,696信息[org.apache.catalina.core.ContainerBase]关闭Spring根WebApplicationContext

2010-01-30 03:25:27,598 INFO [org.apache.catalina.core.ContainerBase] Closing WebApplicationContext of Spring FrameworkServlet 'expertx' 2010-01-30 03:25:27,696 INFO [org.apache.catalina.core.ContainerBase] Closing Spring root WebApplicationContext

是服务器日志中的最后几行.寻找改为发布关闭完成".

are the last few lines in my server log. looking for "Shutdown complete" to be posted instead.

推荐答案

在应用程序上下文中调用close()之前,org.springframework.web.context.ContextLoader记录了这两行.

Those two lines are logged by org.springframework.web.context.ContextLoader, just before it calls close() on your application context.

您可能在应用程序上下文中有一个未响应close()的bean,但是根据您的描述,无法确定可能是什么.

You likely have a bean in the app context which is not responding to the close(), but from your description it's impossible to tell what that might be.

我的建议是将log4j日志增加到DEBUG级别,然后再次尝试关闭. Spring将为它尝试关闭的每个bean记录一个条目,希望您能够看到被阻塞的那个.如果不是很明显,请编辑您的问题,以包括在关闭Spring根WebApplicationContext"之后看到的每个Spring DEBUG级别的日志条目.

My suggestion is to the ramp up your log4j logging to DEBUG level, and then try the shutdown again. Spring will log an entry for each bean it tries to shutdown, and hopefully you'll be able to see the one that's blocking. If it's not obvious, then edit your question to include every Spring DEBUG-level log entry you see after the "Closing Spring root WebApplicationContext" one.

这篇关于jboss关闭未发生,停留在消息:关闭Spring根WebApplicationContext的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆