Spring MVC @Transactional註解方式事務失效的解決辦法
阿新 • • 發佈:2018-12-18
前文提到,最新換了框架,新專案用SpringMVC + Spring JdbcTemplate。搭框架時,發現了一個事務無法正常回滾的問題,記錄如下:
首先展示問題:
Spring applicationContext.xml配置:
- <beanid="dataSource"class="org.springframework.jndi.JndiObjectFactoryBean">
- <propertyname="jndiName">
- <value>java:comp/env/jdbc/will</value>
- </property
- </bean>
- <beanid="jdbcTemplate"class="org.springframework.jdbc.core.JdbcTemplate">
- <propertyname="dataSource"ref="dataSource"/>
- </bean>
- <beanid="txManager"
- class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
- <propertyname="dataSource"ref="dataSource"
- </bean>
- <!-- 事務控制 -->
- <tx:annotation-driventransaction-manager="txManager"/>
Spring mvc.dispatcher.xml配置:
- <!-- 自動掃描的包名 -->
- <context:component-scanbase-package="com.will">
- </context:component-scan>
- <!-- 預設的註解對映的支援 -->
- <mvc:annotation-driven/>
- <!-- 對靜態資原始檔的訪問 -->
- <mvc:default-servlet-handler/>
- <!-- 攔截器
- <mvc:interceptors>
- <beanclass="com.will.mvc.MyInteceptor"/>
- </mvc:interceptors>
- -->
- <!-- 檢視解釋類 -->
- <beanid="viewResolver"
- class="org.springframework.web.servlet.view.UrlBasedViewResolver">
- <propertyname="viewClass"value="org.springframework.web.servlet.view.JstlView"/>
- <propertyname="prefix"value="/WEB-INF/pages/"/>
- <propertyname="suffix"value=".jsp"/>
- </bean>
- @Transactional
- publicboolean save(Person person)
- {
- for(int id: newint[]{2,3})
- {
- personDao.del(id);
- int j = 1/0;
- }
- returnfalse;
- }
本以為大功告成,在執行save方法時,由於1/0 丟擲 java.lang.ArithmeticException: / by zero RuntimeException,導致事務迴歸。However,no way! So crazy~
查了下,發現Spring MVC對於事務配置比較講究,需要額外的配置。解決辦法如下:
需要在 applicationContext.xml增加:
- <context:component-scanbase-package="com.will">
- <context:exclude-filtertype="annotation"expression="org.springframework.stereotype.Controller"/>
- </context:component-scan>
- <context:component-scanbase-package="com.will">
- <context:include-filtertype="annotation"expression="org.springframework.stereotype.Controller"/>
- <context:exclude-filtertype="annotation"expression="org.springframework.stereotype.Service"/>
- </context:component-scan>
由於web.xml中配置:
- <context-param>
- <param-name>contextConfigLocation</param-name>
- <param-value>
- classpath:applicationContext.xml
- </param-value>
- </context-param>
- <listener>
- <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
- </listener>
- <servlet>
- <servlet-name>dispatcher</servlet-name>
- <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
- <init-param>
- <param-name>contextConfigLocation</param-name>
- <param-value>classpath*:/mvc_dispatcher_servlet.xml</param-value>
- </init-param>
- <load-on-startup>1</load-on-startup>
- </servlet>
- <servlet-mapping>
- <servlet-name>dispatcher</servlet-name>
- <url-pattern>*.do</url-pattern>
- </servlet-mapping>
( update 2014.05.27 今天看見一種說法:key word =雙親上下文。不使用ContextLoaderListener監聽器來載入spring的配置,改用DispatcherServlet來載入spring的配置,不要雙親上下文,只使用一個DispatcherServlet就不會出現上述問題。筆者這裡未測過這個辦法,因為我自己的業務需要一個extends ContextLoaderListener的selfListener,有興趣的朋友可以自己測試下這個說法,並歡迎把測試的結果與我交流 :) )
經過以上分析,故可以優化上述配置:
在 applicationContext.xml增加:
- <context:component-scanbase-package="com.will">
- </context:component-scan>
- <context:component-scanbase-package="com.will">
- <context:exclude-filtertype="annotation"expression="org.springframework.stereotype.Service"/>
- </context:component-scan>
經過如上配置,可以發現事務控制部分的日誌如下:
- 2013-09-25 09:53:13,031 [http-8080-2] DEBUG [org.springframework.transaction.annotation.AnnotationTransactionAttributeSource] - Adding transactional method 'save' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
- 2013-09-25 09:53:13,037 [http-8080-2] DEBUG [org.springframework.beans.factory.support.DefaultListableBeanFactory] - Returning cached instance of singleton bean 'txManager'
- 2013-09-25 09:53:13,050 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Creating new transaction with name [com.will.service.impl.PersonServiceImpl.save]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
- 2013-09-25 09:53:13,313 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Acquired Connection [jdbc:mysql://localhost:3306/mvc?useUnicode=true&characterEncoding=UTF-8, UserName=root@localhost, MySQL-AB JDBC Driver] for JDBC transaction
- 2013-09-25 09:53:13,323 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Switching JDBC Connection [jdbc:mysql://localhost:3306/mvc?useUnicode=true&characterEncoding=UTF-8, UserName=root@localhost, MySQL-AB JDBC Driver] to manual commit
- 2013-09-25 09:53:13,327 [http-8080-2] DEBUG [org.springframework.jdbc.core.JdbcTemplate] - Executing prepared SQL update
- 2013-09-25 09:53:13,328 [http-8080-2] DEBUG [org.springframework.jdbc.core.JdbcTemplate] - Executing prepared SQL statement [delete from person where id=?]
- 2013-09-25 09:53:13,348 [http-8080-2] DEBUG [org.springframework.jdbc.core.JdbcTemplate] - SQL update affected 1 rows
- 2013-09-25 09:53:13,363 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Initiating transaction rollback
- 2013-09-25 09:53:13,364 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Rolling back JDBC transaction on Connection [jdbc:mysql://localhost:3306/mvc?useUnicode=true&characterEncoding=UTF-8, UserName=root@localhost, MySQL-AB JDBC Driver]
- 2013-09-25 09:53:13,377 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Releasing JDBC Connection [jdbc:mysql://localhost:3306/mvc?useUnicode=true&characterEncoding=UTF-8, UserName=root@localhost, MySQL-AB JDBC Driver] after transaction
- 2013-09-25 09:53:13,378 [http-8080-2] DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] - Returning JDBC Connection to DataSource
PS:習慣了Structs,對事務處理有點思維定式,這次花費不少時間來解決這個問題。頗為尷尬!