Hibernate / Spring - JUnit因Transactional失败(REQUIRES_NEW)

时间:2016-03-15 19:53:47

标签: java spring hibernate jpa spring-transactions

我们最近决定将某些方法从@Transactional更改为@Transactional(propagation = Propagation.REQUIRES_NEW)

并在 applicationContext.xml

中添加了<tx:annotation-driven proxy-target-class="true"/>

运行应用程序时一切正常,但我们的测试失败,出现以下异常:

2016-03-15 20:44:02 [main] DEBUG org.hibernate.SQL - 
insert 
into
    utfylling_versjon
    (opprettet, utfylling_id, id) 
values
    (?, ?, ?)

2016-03-15 20:44:02 [main] TRACE o.h.type.descriptor.sql.BasicBinder - binding parameter [1] as [TIMESTAMP] - [Tue Mar 15 20:44:02 CET 2016]
2016-03-15 20:44:02 [main] TRACE o.h.type.descriptor.sql.BasicBinder - binding parameter [2] as [BIGINT] - [1216]
2016-03-15 20:44:02 [main] TRACE o.h.type.descriptor.sql.BasicBinder - binding parameter [3] as [BIGINT] - [1217]
2016-03-15 20:44:02 [main] WARN  o.h.e.jdbc.spi.SqlExceptionHelper - SQL Error: 23506, SQLState: 23506
2016-03-15 20:44:02 [main] ERROR o.h.e.jdbc.spi.SqlExceptionHelper - Referential integrity constraint violation: "FK_JA5LSNJNODJIEEC22M3HU3YIS: PUBLIC.UTFYLLING_VERSJON FOREIGN KEY(UTFYLLING_ID) REFERENCES PUBLIC.UTFYLLING(ID) (1216)"; SQL statement:
insert into utfylling_versjon (opprettet, utfylling_id, id) values (?, ?, ?) [23506-191]
2016-03-15 20:44:02 [main] INFO  o.h.e.j.b.internal.AbstractBatchImpl - HHH000010: On release of batch it still contained JDBC statements
2016-03-15 20:44:02 [main] INFO  o.s.t.c.t.TransactionContext - Rolled back transaction for test context [DefaultTestContext@41289e88 testClass = RisikoServiceTest, testInstance = no.sb1.forsikring.seopp.kjerne.fip.RisikoServiceTest@7e8783b0, testMethod = sjekkAtFaktaBlirSatt@RisikoServiceTest, testException = org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint ["FK_JA5LSNJNODJIEEC22M3HU3YIS: PUBLIC.UTFYLLING_VERSJON FOREIGN KEY(UTFYLLING_ID) REFERENCES PUBLIC.UTFYLLING(ID) (1216)"; SQL statement:
insert into utfylling_versjon (opprettet, utfylling_id, id) values (?, ?, ?) [23506-191]]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement, mergedContextConfiguration = [MergedContextConfiguration@d0e4972 testClass = RisikoServiceTest, locations = '{classpath:test-context.xml}', classes = '{}', contextInitializerClasses = '[]', activeProfiles = '{}', propertySourceLocations = '{}', propertySourceProperties = '{}', contextLoader = 'org.springframework.test.context.support.DelegatingSmartContextLoader', parent = [null]]].

    org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint ["FK_JA5LSNJNODJIEEC22M3HU3YIS: PUBLIC.UTFYLLING_VERSJON FOREIGN KEY(UTFYLLING_ID) REFERENCES PUBLIC.UTFYLLING(ID) (1216)"; SQL statement:
    insert into utfylling_versjon (opprettet, utfylling_id, id) values (?, ?, ?) [23506-191]]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement
        at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:255)
        at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:221)
        at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:521)

更具体的

Caused by: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "FK_JA5LSNJNODJIEEC22M3HU3YIS: PUBLIC.UTFYLLING_VERSJON FOREIGN KEY(UTFYLLING_ID) REFERENCES PUBLIC.UTFYLLING(ID) (1216)"; SQL statement:
insert into utfylling_versjon (opprettet, utfylling_id, id) values (?, ?, ?) [23506-191]
    at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
    at org.h2.message.DbException.get(DbException.java:179)

为什么它失败了,因为我们运行了一个需要new的事务?

如果我将其更改回@Transactional,那么一切正常,但我们想要在新的交易中运行

编辑:

以下是代码的一部分。我创建了Utfylling。

Utfylling utfylling = someService.createUtfylling();
//Perform some operations
someService.createUtfyllingVersjon(utfylling);

@Transactional
    public Utfylling createUtfylling() {
        Utfylling utfylling = new Utfylling()
        //some setters
        entityManager.persist(utfylling);
        return utfylling;
    }

然后我调用create UtfyllingVersjon

@Transactional(propagation = Propagation.REQUIRES_NEW)
    public void createUtfyllingVersjon(Utfylling utfylling) {
 UtfyllingVersjon utfyllingVersjon = new UtfyllingVersjon(utfylling);
            entityManager.persist(utfyllingVersjon);
//some more setters
utfylling.getUtfyllingVersjoner().add(utfyllingVersjon);
            entityManager.persist(utfyllingVersjon);
            entityManager.merge(utfylling);
}

Utfylling在createUtfyllingVersjon中分离,所以我必须使用merge。 这在jetty中本地运行代码时有效,但在运行JUnit测试时失败。

这是我的test-context.xml文件

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:tx="http://www.springframework.org/schema/tx"
       xmlns:context="http://www.springframework.org/schema/context"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd
        http://www.springframework.org/schema/tx
        http://www.springframework.org/schema/tx/spring-tx.xsd
        http://www.springframework.org/schema/context
        http://www.springframework.org/schema/context/spring-context.xsd">

    <!-- enable the configuration of transactional behavior based on annotations -->
    <tx:annotation-driven proxy-target-class="true"/>

    <context:annotation-config />
    <context:component-scan base-package="foo.bar"/>

    <bean id="dozerMapper" class="org.dozer.DozerBeanMapper" />

    <bean id="h2DataSource" class="org.apache.commons.dbcp2.BasicDataSource" destroy-method="close">
        <property name="driverClassName" value="org.h2.Driver"/>
        <property name="url" value="jdbc:h2:mem:testdb;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE;"/>
        <property name="username" value="sa"/>
        <property name="password" value=""/>
    </bean>

    <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
        <property name="persistenceXmlLocation" value="META-INF/persistence-test.xml"/>
        <property name="packagesToScan" value="foo.bar" />
        <property name="dataSource" ref="h2DataSource"/>
        <property name="jpaVendorAdapter" ref="jpaVendorAdapter"/>
        <property name="jpaDialect" ref="jpaDialect"/>
        <property name="jpaProperties">
            <props>
                <prop key="hibernate.show_sql">false</prop>
                <prop key="hibernate.hbm2ddl.auto">create</prop>
            </props>
        </property>
    </bean>

    <bean id="jpaVendorAdapter" class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter">
        <property name="database" value="H2"/>
        <property name="databasePlatform" value="org.hibernate.dialect.H2Dialect"/>
        <property name="generateDdl" value="true"/>
        <property name="showSql" value="true"/>
    </bean>

    <bean id="jpaDialect" class="org.springframework.orm.jpa.vendor.HibernateJpaDialect"/>

    <bean id="transactionTemplate" class="org.springframework.transaction.support.TransactionTemplate">
        <property name="transactionManager" ref="transactionManager" />
    </bean>

    <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
        <property name="entityManagerFactory" ref="entityManagerFactory"/>
        <property name="dataSource" ref="h2DataSource"/>
        <property name="jpaDialect" ref="jpaDialect"/>
    </bean>

</beans>

2 个答案:

答案 0 :(得分:2)

这里有两个不同的问题:

为什么会失败?

这是相当简单的:在你的代码中你基本上做了两个插入。当您尝试执行第二次插入时,您会收到:

Referential integrity constraint violation

这是合乎逻辑的,因为您刚刚更改了代码以在单独的事务中执行第二个插入。 此新事务不“看到”前一个插入的记录(仅提交,并且事务内插入在任何给定的事务中都可见),因此外键约束阻止您插入第二排。为什么?因为如果第一个事务因任何原因而被回滚,第二个插入可能导致完整性违规。因此DB完全按照应有的方式行事。为了避免这种情况发生,您需要以某种方式更改代码:

  • 删除FK约束
  • 不要在单独的事务中执行属于一起的插入(可能只使用REQUIRE,而不是REQUIRE_NEW)

为什么您会从测试和主要代码中获得不同的结果?

这有点困难。我唯一的假设是你的主代码自动提交第一个事务,因此使第一个插入对第二个事务可见。虽然您的测试使第一个事务保持挂起(可能最终会回滚),但这会导致上述问题。

答案 1 :(得分:1)

我的猜测:

Spring @Transactional默认传播级别是REQUIERED,所需规格是:&#34;支持当前事务,如果不存在则创建一个新事务。&#34;

单元测试本身在一个事务中运行,createUtfylling连接现有事务,然后createUtfyllingVersion暂停它,打开它自己的事务,它没有看到挂起的更改并触发外键异常。 / p>

在应用程序运行期间,您没有封闭事务,createUtfyllingVersion会立即创建它自己的新事务(因此对于以下调用可以看到更新)