82 | Cannot catch a PersistenceException and continue the transaction the transaction as one that need to be rolled back. I understood that I can overcome it in several ways but those don't work for me. Begin a new (nested) transaction in another method that will be rolled back instead of the first one- doesn't work. I got a message that it couldn't begin a new transaction |
82 | Custom Transaction ManagerHi, I am trying integrate ObjectDB and Quarkus Framework. Quarkus use Narayana/Arjuna transaction manager. ObjectDB doesn't allow me to configure custom JNDI name or Transaction Manager class ... locations, including: java:/TransactionManager javax.transaction.TransactionManager java:comp |
82 | Bug with unique constraint exception not resulting in transaction roll back ObjectDB to roll back the transaction and not persist anything. However, it is persisting both entities ... over more than one transaction. In a managed environment, in which transactions are started and committed by the application server and not be the application, sometimes it is difficult to see when one transaction is ended |
81 | Transaction isolation support? have been unable to find any documentation about how transaction isolation is handled. For example: What happens If I am reading data in transaction A, and then transaction B commits while A is reading ... would run in their own transaction, and the answer would thus depend on the the selected isolation level |
81 | Rollback of several closed transactions to split a transaction into several transactions. But then we need actually a rollback for several transactions. Is there any possibility in the ObjectDB to rollback several closed transactions? btc_es BTC EmbeddedSystems You cannot roll back a committed transaction. In that case, you may want |
81 | One transaction or two? is it more efficient to do everything in one transaction or two? Currently my code looks like ... and adds into separate transactions? I think I remember reading in another forum post that you recommended this, I just wanted to clarify. carr.onstott Carr Onstott Actually one transaction |
16 | Query in nested transaction returns detached entity if lazy-loaded that have been persisted by other transactions from within a transaction that was flushed before ... transactions as a snapshot of the database when flush occurs. Build 2.7.4_04 includes a workaround ... to commit transaction: Optimistic lock failed for object com.btc.ep.base.bl.internal.entities.mapping |
16 | Working with JPA Entity Objects via an EntityManager’s persist method, which must be invoked within an active transaction. On transaction commit ... Entities section. If a managed entity object is modified within an active transaction the change is detected by the owning EntityManager and the update is propagated to the database on transaction |
3 | Step 6: Set the Spring XML> <!-- Add Transaction support --> <bean id="myTxManager" class="org.springframework ... > <!-- Use @Transaction annotations for managing transactions --> <tx:annotation-driven transaction-manager="myTxManager" /> <!-- View resolver --> <bean class= "org.springframework |
3 | Step 6: Set the Spring XML> </bean> <!-- Add Transaction support --> <bean id="myTxManager" class="org ... "/> </bean> <!-- Use @Transaction annotations for managing transactions --> <tx:annotation-driven transaction-manager="myTxManager" /> <!-- View resolver --> <bean class= "org |
