spring-transactions

We have a Spring Transaction rollback issues, where rollback doesn't seems to be working. Within my service layer method which is annotated with @Transactional I call three different DAOImpl classes to insert 3 records. The middle insert do a get from a 4th table to populate a description field but this get failed. I expect the first insert to rollback but it doesn't seems to be happening. Few Points: The 'Get' method throws a Runtime Exception We are using org.springframework.jdbc.datasource.DataSourceTransactionManager and MySQL datasource defined in applicationContext.xml . Beans are

Im using SpringBatch 2.1.7 release core and Infrastructure jars to read a CSV file and save it to DB. Integrated my code with Spring quartz scheduler to run for every minute, The Batch is working fine with reading and writing but its failing with the error "org.springframework.dao.OptimisticLockingFailureException: Attempt to update step execution id=1 with wrong version (2), where current version is 1" due to Tx conflicts. Please suggest how can i resolve this issue. I had this same exception. org.springframework.dao.OptimisticLockingFailureException: Attempt to update step execution id=0

I am using Spring and Hibernate in my application and using Spring Transaction. So I have a service layer with annotation @Transaction on methods and DAO layer having methods for database query. @Transactional(readOnly = false) public void get(){ } The issue is when I want to save an object in the database,then I have to use session.flush() at the end of DAO layer method. Why? I think if I have annotated @Transaction , then Spring should automatically commit the transaction on completion of the service method. DAO layer : public BaseEntity saveEntity(BaseEntity entity) throws Exception { try {

I have an application built on Spring. I let the Spring do the all @Transactional magic and everything works fine as long as I operate on my entities that are mapped to Java objects. However, when I want to do some custom job on a table that is not mapped to any of my Java entities, I'm stuck. Some time ago, I found a solution to execute a custom query like this: // em is instance of EntityManager em.getTransaction().begin(); Statement st = em.unwrap(Connection.class).createStatement(); ResultSet rs = st.executeQuery("SELECT custom FROM my_data"); em.getTransaction().commit(); When I try this

In a nutshell My command line Java application copies data from one datasource to another without using XA. I have configured two separate datasources and would like a JUnit test that can rollback data on both datasources. I use DBUnit to load data into the "source" database, but I cannot get this to rollback. I can get the "target" datasource to rollback. My Code Given this config... <tx:annotation-driven /> <!-- note the default transactionManager name on this one --> <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager"> <property name=

I found the following thread: How exactly JdbcTemplate with TransactionManager works together? The first sentence of that: As far as I understood DataSourceTransactionManager binds a JDBC connection from the specified DataSource to the current thread, allowing for one thread-bound Connection per DataSource. If it's a pool of connections, it will take one of the available connections. ... is exactly what I want to know. When using a transaction manager, do you end up with each thread having it's own single connection? Also, how long does that connection live? Does the same thread use the same

I'm using Spring with JPA. I have @EnableAsync and @EnableTransactionManagement turned on. In my user registration service method, I have a few other service methods I call that are annotated @Async . These methods do various things like sending a welcome email and registering the newly minted user with our third party payment system. Everything works well until I want to verify that the third party payment system successfully created the user. At that point, the @Async method attempts to create a UserAccount (that references the newly minted User ) and errors out with a javax.persistence