About Transaction

41-50 of 200Refresh
Issue
25

Removed entities can be found by query in the same transaction

Hello, we opened a transaction, load an entity from database and removed this entity by em.remove ... : ObjectDB uses snapshots in order to isolate transactions, i.e. to hide uncommitted flush changes of one transaction from other transactions, but still make them available to that transaction
Forum
25

Visibility of changes in Transaction is not visible to a JPA QL Query

I have two simple Entities ( see attachment ) and a simple SLSB with container managed transactions ... InitialContext();    javax.transaction.UserTransaction tx = (javax.transaction.UserTransaction) context ... ();   } catch   The problem is that the items that I add in the transaction are not visible when I
Forum
25

Performance in large transactions

Hello, we have a performance problem when we use a large transaction. Let's do exactly the same in several transactions the ObjectDB works much faster. In our use case, we create many new entities ... (FlushModeType.AUTO); EntityTransaction transaction = entityManager.getTransaction
Forum
25

javax.transaction.Synchronization with Java SE 10.0.1

/transaction/Synchronization     at java.base/java.lang.ClassLoader.defineClass1(Native Method ... ) Caused by: java.lang.ClassNotFoundException: javax.transaction.Synchronization     at java.base ... with this footprint [module java.transaction, location=jrt:/java.transaction] and within this module
Issue
24

Query in nested transaction returns detached entity if lazy-loaded

new objects that have been persisted by other transactions from within a transaction ... manages flushed transactions as a snapshot of the database when flush occurs. Build 2.7.4_04 includes ... in our tool. Caused by: com.objectdb.o._RollbackException: Failed to commit transaction: Optimistic
Forum
24

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. This could happen if the operation is spread over more than one transaction. In a managed environment, in which transactions are started and committed by the application server and not
Forum
24

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
Forum
24

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. Actually one transaction eliminates some overhead
Forum
24

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 ... their own transaction, and the answer would thus depend on the the selected isolation level for the transaction in
Issue
24

ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed

a transaction (including the entity manager) the ODB file writer still holds a reference to entities ... are enhanced. The entity DBVectorStepBlockCollectionImpl was modified and then the transaction ... , if we execute several transactions on the identical entity manager. Also triggering the Garbage