解决Could not commit JPA transaction RollbackException: Transaction marked as rollbackOnly
2017-09-07 18:08
916 查看
解决Could not commit JPA transaction RollbackException: Transaction marked as rollbackOnly
Could not commit JPA transaction RollbackException: Transaction marked as rollbackOnly:出现该错误的原因是使用@Transactional事务托管注解的方法或类事务已经被标记为值回滚,且不能再设置为不会滚。首先了解下@Transactional注解:
@Transactional注解
@Transactional属性
属性 | 类型 | 描述 |
---|---|---|
value | String | 可选的限定描述符,指定使用的事务管理器 |
propagation | enum: Propagation | 可选的事务传播行为设置 |
isolation | enum: Isolation | 可选的事务隔离级别设置 |
readOnly | boolean | 读写或只读事务,默认读写 |
timeout | int (in seconds granularity) | 事务超时时间设置 |
rollbackFor | Class对象数组,必须继承自Throwable | 导致事务回滚的异常类数组 |
rollbackFor | ClassName 类名数组,必须继承自Throwable | 导致事务回滚的异常类名字数组 |
noRollbackFor | Class对象数组,必须继承自Throwable | 不会导致事务回滚的异常类数组 |
noRollbackFor | ClassName 类名数组,必须继承自Throwable | 不会导致事务回滚的异常类名字数组 |
@Transactional 可以作用于接口、接口方法、类以及类方法上。当作用于类上时,该类的所有 public 方法将都具有该类型的事务属性,同时,我们也可以在方法级别使用该标注来覆盖类级别的定义。
虽然 @Transactional 注解可以作用于接口、接口方法、类以及类方法上,但是 Spring 建议不要在接口或者接口方法上使用该注解,因为这只有在使用基于接口的代理时它才会生效。另外, @Transactional 注解应该只被应用到 public 方法上,这是由 Spring AOP 的本质决定的。如果你在 protected、private 或者默认可见性的方法上使用 @Transactional 注解,这将被忽略,也不会抛出任何异常。
默认情况下,只有来自外部的方法调用才会被AOP代理捕获,也就是,类内部方法调用本类内部的其他方法并不会引起事务行为,即使被调用方法使用@Transactional注解进行修饰。
@Transactional(readOnly = true) public class DefaultFooService implements FooService { public Foo getFoo(String fooName) { // do something } // these settings have precedence for this method //方法上注解属性会覆盖类注解上的相同属性 @Transactional(readOnly = false, propagation= Propagation.REQUIRES_NEW) public void updateFoo(Foo foo) { // do something } }
那么我们的问题就是如果使用@Transactional注解,将事务交给Spring处理的话,因为@Transactional默认设置为回滚,无论如何设置rollbackFor、noRollbackFor都会将事务回滚。但是代码执行的时候,似乎SQL语句没有执行回滚就结束了。所以接抛出该异常。
解决方法是从entityManager中得到EntityManagerFactory再创建一个新的EntityManager,然后开始执行事务:
@PersistenceContext private EntityManager entityManager; /** * 获取 entityManager * @return the entityManager */ public EntityManager getEntityManager() { return entityManager; } /** * 设置 entityManager * @param entityManager the entityManager to set */ public void setEntityManager(EntityManager entityManager) { this.entityManager = entityManager; } private int execute(String sql,EntityManager em) { EntityManager em = getEntityManager().getEntityManagerFactory().createEntityManager(); em.getTransaction().begin(); ....... em.getTransaction().commit(); return 1; }
同时还能解决:javax.persistence.TransactionRequiredException: Executing an update/delete query异常,因为此处新建了一个事务处理。而该异常是没有事务处理Spring抛出来的异常,一举两得!
相关文章推荐
- 解决Could not commit JPA transaction RollbackException: Transaction marked as rollbackOnly
- 解决Could not commit JPA transaction RollbackException: Transaction marked as rollbackOnly
- Could not commit JPA transaction; nested exception is javax.persistence.RollbackException 解决方法
- JPA出现Transaction marked as rollback only异常 总结
- UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
- java:Transaction marked as rollbackOnly异常原因及解决
- javax.persistence.RollbackException: Transaction marked as rollbackOnly异常出现的原因以及避免方法
- Transaction rolled back because it has been marked as rollback-only分析解决方法
- spring事务(Transaction )报 marked as rollback-only异常的原因及解决方法
- JPA transaction marked as rollbackonly错误
- Transaction rolled back because it has been marked as rollback-only
- Transaction rolled back because it has been marked as rollback-only异常
- Transaction rolled back because it has been marked as rollback-only”
- Transaction rolled back because it has been marked as rollback-only
- 解决 org.hibernate.HibernateException: Could not obtain transaction-synchronized Session for cu
- Transaction rolled back because it has been marked as rollback-only
- 解决Could not retrieve transaction read-only status from server
- 【Spring】21、用spring目标对象处理Transaction rolled back because it has been marked as rollback-only
- Transaction rolled back because it has been marked as rollback-only”
- Transaction rolled back because it has been marked as rollback-only