如何在@Transactional方法中手动强制提交?

时间:2014-06-21 04:02:36

标签: java spring jpa spring-data spring-transactions

我使用Spring / Spring-data-JPA并发现自己需要在单元测试中手动强制提交。我的用例是我正在进行多线程测试,我必须使用在生成线程之前保留的数据。

不幸的是,鉴于测试是在@Transactional事务中运行的,即使是flush也不会使生成的线程可以访问它。

   @Transactional   
   public void testAddAttachment() throws Exception{
        final Contract c1 = contractDOD.getNewTransientContract(15);
        contractRepository.save(c1);

        // Need to commit the saveContract here, but don't know how!                
        em.getTransaction().commit();

        List<Thread> threads = new ArrayList<>();
        for( int i = 0; i < 5; i++){
            final int threadNumber = i; 
            Thread t =  new Thread( new Runnable() {
                @Override
                @Transactional
                public void run() {
                    try {
                        // do stuff here with c1

                        // sleep to ensure that the thread is not finished before another thread catches up
                        Thread.sleep(1000);
                    } catch (InterruptedException e) {
                        // TODO Auto-generated catch block
                        e.printStackTrace();
                    }
                }
            });
            threads.add(t);
            t.start();
        }

        // have to wait for all threads to complete
        for( Thread t : threads )
            t.join();

        // Need to validate test results.  Need to be within a transaction here
        Contract c2 = contractRepository.findOne(c1.getId());
    }

我尝试过使用实体管理器,但在我这样做时收到错误消息:

org.springframework.dao.InvalidDataAccessApiUsageException: Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead; nested exception is java.lang.IllegalStateException: Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead
    at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:293)
    at org.springframework.orm.jpa.aspectj.JpaExceptionTranslatorAspect.ajc$afterThrowing$org_springframework_orm_jpa_aspectj_JpaExceptionTranslatorAspect$1$18a1ac9(JpaExceptionTranslatorAspect.aj:33)

有没有办法提交交易并继续下去?我一直找不到允许我拨打commit()的方法。

3 个答案:

答案 0 :(得分:49)

我在测试hibernate事件监听器时有一个类似的用例,它只在commit上调用。

解决方案是将代码保存为另一个使用REQUIRES_NEW注释的方法。 (在另一个类中)这样生成一个新事务,并在方法返回后发出flush / commit。

Tx prop REQUIRES_NEW

请记住,这可能会影响所有其他测试!因此,请相应地编写它们,或者您需要确保在测试运行后可以进行清理。

答案 1 :(得分:22)

为什么不使用spring TransactionTemplate以编程方式控制事务?您还可以重新构建代码,以便每个“事务块”都有自己的@Transactional方法,但鉴于它是一个测试,我会选择对您的事务进行编程控制。

另请注意,runnable上的@Transactional注释不起作用(除非您使用aspectj),因为runnables不是由spring管理的!

@RunWith(SpringJUnit4ClassRunner.class)
//other spring-test annotations; as your database context is dirty due to the committed transaction you might want to consider using @DirtiesContext
public class TransactionTemplateTest {

@Autowired
PlatformTransactionManager platformTransactionManager;

TransactionTemplate transactionTemplate;

@Before
public void setUp() throws Exception {
    transactionTemplate = new TransactionTemplate(platformTransactionManager);
}

@Test //note that there is no @Transactional configured for the method
public void test() throws InterruptedException {

    final Contract c1 = transactionTemplate.execute(new TransactionCallback<Contract>() {
        @Override
        public Contract doInTransaction(TransactionStatus status) {
            Contract c = contractDOD.getNewTransientContract(15);
            contractRepository.save(c);
            return c;
        }
    });

    ExecutorService executorService = Executors.newFixedThreadPool(5);

    for (int i = 0; i < 5; ++i) {
        executorService.execute(new Runnable() {
            @Override  //note that there is no @Transactional configured for the method
            public void run() {
                transactionTemplate.execute(new TransactionCallback<Object>() {
                    @Override
                    public Object doInTransaction(TransactionStatus status) {
                        // do whatever you want to do with c1
                        return null;
                    }
                });
            }
        });
    }

    executorService.shutdown();
    executorService.awaitTermination(10, TimeUnit.SECONDS);

    transactionTemplate.execute(new TransactionCallback<Object>() {
        @Override
        public Object doInTransaction(TransactionStatus status) {
            // validate test results in transaction
            return null;
        }
    });
}

}

答案 2 :(得分:4)

我知道由于这个丑陋的匿名内部类使用TransactionTemplate看起来并不好看,但是出于某种原因我们想要一个测试方法事务恕我直言,它是最灵活的选项。

在某些情况下(取决于应用程序类型),在Spring测试中使用事务的最佳方法是在测试方法上关闭@Transactional。为什么?因为@Transactional可能导致许多误报测试。您可以查看此sample article以查找详细信息。在这种情况下,当我们想要控制时,TransactionTemplate可以完美地控制事务边界。