Home » Search

About transaction

71-80 of 200Refresh
Issue
16

Inefficient memory usage with very large transactions

When a large transaction is committed, ObjectDB increases some internal structures, i.e. allocates more memory, but from that point the structures remain big and the memory is not released even if all the next transactions are small. This problem was found during a heap analysis (see #9 in
Forum
16

NegativeArraySizeException on commiting a transaction

Hi, we started to get a java.lang.NegativeArraySizeException from ObjectDB upon changing an object in the DB and committing the transaction. I tried to repair the DB file with Database Doctor ... from the ProjectVersionHistory, so only 20 remained and since then my changing transactions
Issue
16

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

The following error is reported for objectdb-2.6.9.jar: Failed to commit transaction: Failed to set numeric value of field property com.greensoft.objectdb.test.entity.Element.id using reflection ... .6.9] javax.persistence.RollbackException Failed to commit transaction: Failed to set numeric value
Forum
16

remove() and persist() in same transaction => Attempt to reuse an existing primary key value

transaction: first remove additional Data -> The special Entity (with id 1) is empty and we remove ... and then in the same transaction persisting another object with the same primary key of the removed object
JPA Doc
16

javax.persistence.EntityManager

). If this method is called when the entity manager is associated with an active transaction, the persistence context remains managed until the transaction completes. Throws: IllegalStateException - if the entity ... : the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback
Forum
16

CM Transaction Implementation

Hi All, How to implement Container Managed Transaction using Glassfish / Weblogic server. Please provide us the step by step instruction, how ti achieve it       Please check the following tutorial: http://www.objectdb.com/tutorial/jpa/ee umesh
Forum
16

com.objectdb.o._RollbackException: Failed to commit transaction

Check the Exception below: (occurs sometimes, ObjectDB 2.3.6_14) com.objectdb.o._RollbackException: Failed to commit transaction: at com.objectdb.o.JPE.g(JPE.java:89) ~[JPE.class:na] at com.objectdb.o.ERR.f(ERR.java:59) ~[ERR.class:na] at com.objectdb.o.OBC
Forum
16

Failed to commit transaction: Java heap space (error 613)

.RollbackException Failed to commit transaction: Java heap space (error 613) We are using ObjectDB 2.4.6_10
Issue
16

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

Hello, we've encountered a problem leading to memory leaks. We found that after closing a transaction (including the entity manager) the ODB file writer still holds a reference to entities. Performing similar calls repeatedly hence increases the number of references to entities not longer needed in
Forum
16

Query problem after transaction commit

I have a machine running the objectdb server and the client on another machine connect to it. The client program can connect to the server and query to get all the records. However, after transaction.begin ... persist(p) .. commit of a new object, my client program can no longer retrieve the old