admin管理员组文章数量:1289828
I am facing a problem using programmatic or/and declarative transaction management using spring in a project that I've been working.
Because the Entities "area created at runtime" based in a SQL-Schema (bytebuddy and jdbc) that obligated me to extends the DefaultPersistenceUnitManager class and the LocalContainerEntityManagerFactoryBean class from spring framework.
When i started the unit testing beginning with EntityManager (PersistenceContext) and transaction demarcation using Hibernate the tests running well.
When I declared a PlatformTransactionManager(JpaTransactionManager) to delegate to Spring to manage the transaction for save/flush/delete operations the test fires the exception bellow.
Since i have to manipulate the classloader using bytebuddy, i was wondering the the TransactionManager(JpaTransactionManager) depends on some particular feature of the LocalContainerEntityManagerFactoryBean like the VendorAdapter (HibernateVendorAdapter) or
SpringHibernateJpaPersistenceProvider that was also modified in the project.
For Example: using declarative transaction management , the TransactionManager attribute is null in the TransactionInterceptor and in programmatic transaction management it fires the exception bellow.
the part of interest of the code that extends Spring Classes is in the link
Regards,
Any clue about Spring TransactionManagement internals might Help.
2025-02-20T14:45:56.637-03:00 DEBUG 45462 --- [ main] o.h.e.t.internal.TransactionImpl : begin 2025-02-20T14:45:56.639-03:00 DEBUG 45462 --- [ main] .postgresql.jdbc.PgConnection : setAutoCommit = false 2025-02-20T14:45:57.783-03:00 DEBUG 45462 --- [ main] .hibernate.orm.sql.exec : Skipping reading Query result cache data: cache-enabled = false, cache-mode = IGNORE 2025-02-20T14:45:57.842-03:00 DEBUG 45462 --- [ main] .hibernate.SQL : select sdt1_0.simple_key,sdt1_0.simple_date,sdt1_0.simple_time,sdt1_0.simple_times_zone,sdt1_0.simple_timestamp,sdt1_0.simple_timestamp_zone from simple_date_table sdt1_0 where sdt1_0.simple_key=? 2025-02-20T14:45:57.948-03:00 DEBUG 45462 --- [ main] .hibernate.orm.results : Initializer list:
.nanotek.data.SimpleDateTable -> EntityJoinedFetchInitializer(.nanotek.data.SimpleDateTable)@75465588 (SingleTableEntityPersister(.nanotek.data.SimpleDateTable))2025-02-20T14:45:58.160-03:00 DEBUG 45462 --- [ main] cResourceLocalTransactionCoordinatorImpl : JDBC transaction marked for rollback-only (exception provided for stack trace)
java.lang.Exception: exception just for purpose of providing stack trace at .hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.markRollbackOnly(JdbcResourceLocalTransactionCoordinatorImpl.java:309) ~[hibernate-core-6.6.5.Final.jar:6.6.5.Final] at .hibernate.engine.transaction.internal.TransactionImpl.markRollbackOnly(TransactionImpl.java:203) ~[hibernate-core-6.6.5.Final.jar:6.6.5.Final] at .hibernate.engine.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:224) ~[hibernate-core-6.6.5.Final.jar:6.6.5.Final] at .springframework.orm.jpa.JpaTransactionManager$JpaTransactionObject.setRollbackOnly(JpaTransactionManager.java:716) ~[spring-orm-6.2.2.jar:6.2.2] at .springframework.orm.jpa.JpaTransactionManager.doSetRollbackOnly(JpaTransactionManager.java:615) ~[spring-orm-6.2.2.jar:6.2.2] at .springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:906) ~[spring-tx-6.2.2.jar:6.2.2]
本文标签: Spring Programmatic Transaction ManagementProblem using programmatic transactionStack Overflow
版权声明:本文标题:Spring Programmatic Transaction Management - Problem using programmatic transaction - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1741414413a2377426.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论