ObjectDB Database Search

with expiration time. For example, if you know that transactions that need that specific lock ... , and if the locking client unexpectedly fails during that transaction (which is expected to be rare

Hi, I frequently see exceptions during development such as com.objectdb.o._RollbackException: Failed to commit transaction : Optimistic lock failed for object com.example.MyEntity#3 (object ... . If you still get the error then you can try waiting before trying the transaction again or trying multiple times. jgleoj23 Joseph Gardi

is even slower, but I found that using smaller transactions (2,000 instead of 10,000 entity objects per transaction ) brings 1-thread and 4-threads runs to equivalent results, so maybe in this test 4

Hi, We are currently looking at ObjectDB for high performance / high volume transaction processing system. However we want to work on one of the aspects that is the data should be able to pulled out of the ObjectDB to some sort of Big Data File system or Relation DB for reporting / analytics

. The prototype is running in a  Tomcat server with a RESOURCE_LOCAL transaction scope over a plain

) Is this because I'm somehow not closing a transaction properly, or a PersistenceManager, or

a console test case link this evening): Issue #1924 - ObjectDB-2.6.9: Failed to commit transaction

.springframework. transaction .interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java

In our use case we want to find some entity types always again very quickly by primary key or query in many short transactions . The entity MyEntity1 and its relationships to MyEntity2/MyEntity3 was load and the entity MyEntity1 is taken in the second level cache, the other entity types not

They are always closed. My @ Transactional is on service level, it is opend to load all needed

Cloud HIMS is a JSF/JPA (EclipseLink 2.3)/MySQL application designed to capture data in Health Care Centres across Sri Lanka. We've recently migrated to ObjectDB to improve performance. Despite the migration, we're experiencing general performance issues across all transactions . As requested in

://stackoverflow.com/questions/22183175/javafx-tableview-with- transaction -support They are on JPA in general with JavaFX.   support Support

()=com.objectdb.o._RollbackException: Failed to commit transaction : GC overhead limit exceeded e

.locks.ReentrantReadWriteLock locks, and varying the length (number of actions) within a transaction

factors include the number of concurrent users, transaction duration, query patterns, index usage

the changes after that? oudjanef Farid Oudjane Yes, make the updates within an active transaction and commit. support Support Thanks. Farid oudjanef Farid Oudjane

which acts as archiving device for processing and storing logs, records and transactions . Hardware

other value) should be done in the same transaction , to avoid a reference from User to a deleted Profile

How to disable Transparent Update. I have done 2 task in a single transaction . 1. Find a entity by a em.find(Class cls,Object o) and change some fields.(not updating) 2. Persist a new entity. But i found the in 1st case the changed value was updated. I have attached the sample program

with the transaction commited and manager closed at the end of each action

.persistence.RollbackException Failed to commit transaction : (error 613)). Do you have an idea? package

a simple console application) that update the objects in a loop within an active transaction

list, and each transaction or query execution could use several values lists, so high database activity

Failed to commit transaction : Unique constraint (org.wroth.ws.signup.Request[username]) failed

.springframework. transaction .interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110

.LocalContainerEntityManagerFactoryBean; import org.springframework. transaction .annotation

. Please run the main() in the testobjectdb.Main class. In this method: # in a transaction

. Persisting bulk of objects every transaction (instead of a transaction per entity object). support

Added support for integration with WebSphere / Liberty application server. Fixed deletin g large transaction temporary files (in the experimental large transactions feature ). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects. Fixed a query

(and our application), we add for all entities an instance in the database and rollback the transaction . (As ... an instance in the database and rollback the transaction . This step is just to increase

;     javax. transaction          jta  

When using JQL-Update Queries it is basically not working without calling entityManager.clear() after a transaction commit. When the clear() method isn't called the entityManager will never return a container the updated Entities. Scenario 1 : Disabled L2 Cache, updating elements using UPDATE

and db files ( transaction is rolled back )   The packages were all enhanced ( static weaving

to commit transaction : Unique constraint (id.co.ecoin.test.objectdb.ObjectDbTest$OdbByteArray[key

is incomplete. In that case the last record is ignored (since it represents a transaction that has not

#2750 ). Fixed an error on closing an  EntityManager  with non-comitted flushed transaction

: on accessing lazy loaded relationships outside a transaction , after a query, from Glassfish forum thread

an attachment via addAttachment() method and checks in another transaction if this change was written or not