Xml代码 [转]Spring配置之OpenSessionInViewFilter [转]Spring配置之OpenSessionInViewFilter[转]Spring配置之OpenSessionInViewFilter
  1. <!--Hibernate Open Session in View Filte-->  
  2. <filter>  
  3.     <filter-name>hibernateFilter</filter-name>  
  4.     <filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>  
  5.     <!-- singleSession默认为true,若设为false则等于没用OpenSessionInView -->  
  6.     <init-param>  
  7.         <param-name>singleSession</param-name>  
  8.         <param-value>true</param-value>  
  9.     </init-param>  
  10. </filter>  
  11. <filter-mapping>  
  12.     <filter-name>hibernateFilter</filter-name>  
  13.     <url-pattern>/*</url-pattern>  
  14. </filter-mapping>   
	<!--Hibernate Open Session in View Filte-->
	<filter>
		<filter-name>hibernateFilter</filter-name>
		<filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>
		<!-- singleSession默认为true,若设为false则等于没用OpenSessionInView -->
		<init-param>
			<param-name>singleSession</param-name>
			<param-value>true</param-value>
		</init-param>
	</filter>
	<filter-mapping>
		<filter-name>hibernateFilter</filter-name>
		<url-pattern>/*</url-pattern>
	</filter-mapping>	

2,applicationContext.xml配置openSessionInViewInterceptor
Xml代码 [转]Spring配置之OpenSessionInViewFilter [转]Spring配置之OpenSessionInViewFilter[转]Spring配置之OpenSessionInViewFilter
  1. <bean id="openSessionInViewInterceptor"  
  2.     class="org.springframework.orm.hibernate3.support.OpenSessionInViewInterceptor">  
  3.     <property name="sessionFactory" ref="sessionFactory" />  
  4. </bean>  
	<bean 
		class="org.springframework.orm.hibernate3.support.OpenSessionInViewInterceptor">
		<property name="sessionFactory" ref="sessionFactory" />
	</bean>


三、注意
尽 管Open Session In View看起来还不错,其实副作用不少。看回上面OpenSessionInViewFilter的doFilterInternal方法代码,这个方法实际上是被父类的doFilter调用的,因此,我们可以大约了解的OpenSessionInViewFilter调用流程:

request(请求)->open session并开始transaction->controller->View(Jsp)->结束transaction并 close session.

一切看起来很正确,尤其是在本地开发测试的时候没出现问题,但试想下如果流程中的某一步被阻塞的话,那在这期间connection就一直被占用而不释放。最有可能被阻塞的就是在写Jsp这步,一方面可能是页面内容大,response.write的时间长,另一方面可能是网速慢,服务器与用户间传输时间久。当大量这样的情况出现时,就有连接池连接不足,造成页面假死现象。

Open Session In View是个双刃剑,放在公网上内容多流量大的网站请慎用

相关文章: