springmvc + shiro 框架遇到的问题

springmvc + shiro 框架遇到的问题

尝试解决问题

1、查询容器日志及应用日，均无报错信息
2、启动参数增加-verbrose:class 打印启动类加载，找到如下日志

Oct 18, 2018 10:25:57 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [AsyncAppender-Worker-Thread-4] but has failed to stop it. This is very likely to create a memory leak.
Oct 18, 2018 10:25:57 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [AsyncAppender-Worker-Thread-5] but has failed to stop it. This is very likely to create a memory leak.
Oct 18, 2018 10:25:57 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [AsyncAppender-Worker-Thread-6] but has failed to stop it. This is very likely to create a memory leak.
Oct 18, 2018 10:25:57 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [AsyncAppender-Worker-Thread-7] but has failed to stop it. This is very likely to create a memory leak.
Oct 18, 2018 10:25:57 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [AsyncAppender-Worker-Thread-8] but has failed to stop it. This is very likely to create a memory leak.
Oct 18, 2018 10:25:57 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [AsyncAppender-Worker-Thread-9] but has failed to stop it. This is very likely to create a memory leak.
[Loaded sun.reflect.UnsafeObjectFieldAccessorImpl from /opt/jdk1.8.0_151/jre/lib/rt.jar]

以上日志打印了两遍，发现tomcat也启动了两遍，貌似在循环启动。。。

后查看项目配置文件得以解决，主要涉及到web.xml,及shiro.xml文件

web.xml文件内容

<context-param>
		<param-name>contextConfigLocation</param-name>
		<param-value>classpath:application.xml</param-value>
	</context-param>
<servlet>
		<servlet-name>spring</servlet-name>
		<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
		<init-param>
			<param-name>contextConfigLocation</param-name>
			<param-value>classpath:spring-servlet.xml</param-value>
		</init-param>
		<load-on-startup>1</load-on-startup>
	</servlet>
	<servlet-mapping>
		<servlet-name>spring</servlet-name>
		<url-pattern>/*</url-pattern>
	</servlet-mapping>
<filter>
		<filter-name>shiroFilter</filter-name>
		<filter-class>
			org.springframework.web.filter.DelegatingFilterProxy
		</filter-class>
		<init-param>
			<param-name>targetFilterLifecycle</param-name>
			<param-value>true</param-value>
		</init-param>
	</filter>
	<filter-mapping>
		<filter-name>shiroFilter</filter-name>
		<url-pattern>/roleCheck/*</url-pattern>
		<dispatcher>REQUEST</dispatcher>
		<dispatcher>FORWARD</dispatcher>
	</filter-mapping>

spring-servlet.xml

遂怀疑报错跟导入的spring文件先后顺序有关，将import相关文件移到application.xml文件后能正常启动应用

心想这回没问题了，然鹅并不是，调试发现新加的shiro
filter中的局部属性未初始化成功

后翻阅spring与springmvc相关资料，大致了解下来应用启动起来后，会初始化两个容器，一个是spring主容器，一个是mvc的子容器，它是独立于spring容器的。