ObjectDB Database Search

51-100 of 200 results

Access entity version before commit transaction

commiting the transaction : 1. Change entity field e.g. from a to b 2. Create a change entry in database ... the transaction before commiting it. How can I achieve this? If I add something to a collection ... field it doesn´t. I tried transaction .flush() in combination with transaction .refresh(entity

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

transactions which is called by a trivial servlet. Inside a UserTransaction I add a number of items then check ... context = new InitialContext();    javax. transaction .UserTransaction tx = (javax. transaction ... transaction I find it, even though I don't set the FlushMode. So in that case I can see the results

javax.transaction.Synchronization with Java SE 10.0.1

: javax/ transaction /Synchronization     at java.base/java.lang.ClassLoader.defineClass1 ... : java.lang.ClassNotFoundException: javax. transaction .Synchronization     at java.base ... resolve) there is found a LoadedModule with this footprint [module java. transaction , location=jrt:/java

Bug with unique constraint exception not resulting in transaction roll back

would expect ObjectDB to roll back the transaction and not persist anything.  ... over more than one transaction . In a managed environment, in which transactions are started and committed ... to see when one transaction is ended and another one begins. if you are sure that there is a problem, you may try

Custom Transaction Manager

Hi, 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

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

Best setup for huge amount of transactions

transactions for each edit of the entity: try {      DefaultConnectionManager ... to begin a new transaction when a transaction is active [PMImpl] at com.objectdb.o ._PersistenceException ... .java:56) Thanks, Martin itsme Martin Petzold Each transaction takes around 30-100ms at the moment

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

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 ... database, A and B would run in their own transaction , and the answer would thus depend

One transaction or two?

is it more efficient to do everything in one transaction or two? Currently my code looks like ... (); } } Should I separate the deletes and adds into separate transactions ? I think I remember reading ... Onstott Actually one transaction eliminates some overhead but may require more RAM if you have many large

Populating entity id before transaction commit

Hi, I have a question about populating auto generated id before transaction commit. We are using OBD with Spring and transactions are managed by Spring. The problem is, that we have custom ... transaction is committed so all returned entities are not populated with ID in this context

Update entity without first opening a transaction

Hi everyone, I want to update an entity in my program without having to open a transaction , do the modifications and commit the transaction . I want to have a managed entity that is in sync ... transactions for updating the content of a database. But if you use Java EE or Spring, the container may manage the transactions automatically. support Support

javax.transaction-api-1.3.jar and javax.persistence-api.2.2.jar

Hi, I notice that objectdb zip file has: javax. transaction -api-1.3.jar However that library has moved to jakarta. transaction -api and is now on version 2.0.1 Questions: a) Do I need this library at all? b) If I do need it, do I use jakarta. transaction -api 1.3 or 2.0.1? Similarly java

Is it possible to using JDO and distributed transaction?

I'am new to study JDO. Can and How I use JDO an distributed transaction ?(multiple database ... Reference Documentation       JCA, JTA, and JDO Transactions - Using ... ;    btpka3 ZhangLiangLiang ObjectDB supports distributed transactions and JTA through JPA

Query for objects persisted within the same transaction

I have a question concerning reading uncommited entities with query, within active transaction . For example, I read data from file. Each line contains value of one of entity's attributes ... and persisted withing current transaction is invisible to future queries in this transaction , unless

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 and between the creations we call a select query. The execution of the query becomes slower at each

remove & persist in same transaction => Attempt to reuse an existing primary key value

the same transaction : first remove additional Data - The special Entity (with id 1) is empty and we remove ... removing an entity object and then in the same transaction persisting another object with the same primary

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 ... , so only 20 remained and since then my changing transactions are working fine on that original object

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.onObjectDBError(OBC.java:1493) ~[OBC

Failed to commit transaction: Attempt to reuse an existing primary key value (613)

.RollbackException Failed to commit transaction : Attempt to reuse an existing primary key value

Querys without Transaction

Hello, are querys faster, if we use the entity manager without transaction , since we need only read-only entities. btc_es BTC EmbeddedSystems There is no much difference, but report queries , i.e. queries that return simple value fields rather than entity objects are more efficient as

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

.RollbackException Failed to commit transaction : Java heap space (error 613) We are using ObjectDB 2

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

Max transaction size

What’s the max transaction size, or how is it determined? Trianglehead Json Error The main limit is the available memory in the JVM. There is no hard limit. support Support

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       umesh umesh Please check the following tutorial: http://www.objectdb.com/tutorial/jpa/ee support Support

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 ... explanation on the change in build 2.7.4_04: ObjectDB uses snapshots in order to isolate transactions , i.e. to hide uncommitted flush changes of one transaction from other transactions , but still make

jakarta.persistence.PersistenceUnitTransactionType

: Constable , Comparable , Serializable Enumerates the possible approaches to transaction management in Jakarta Persistence. An EntityManager may be a JTA entity manager, where transaction management is done via JTA, or it may be a resource-local entity manager, where transaction management is performed

Query in nested transaction returns detached entity if lazy-loaded

new objects that have been persisted by other transactions from within a transaction that was flushed ... manages flushed transactions as a snapshot of the database when flush occurs. Build 2.7.4_04 includes ... : Failed to commit transaction : Optimistic lock failed for object com.btc.ep.base.bl.internal.entities

Transaction size limit

Although I read in this post https://www.objectdb.com/forum/2606 that the size of the transaction has no hard limit, our experience shows that we can not commit a transaction exceeding 2GB even though the ObjectDB server runs with Xmx15G. We get the following exception in our JDO transaction in

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 ... DBVectorStepBlockCollectionImpl was modified and then the transaction will be committed. em.getTransaction ... which hold much memory, if we execute several transactions on the identical entity manager

Unexpected exception (Error 990) - Merge with no Transaction

I am frequently having an error when merging a detached object outside of a transaction ... : Attempt to modify an object with no active transaction when NontransactionalWrite is disabled: com ... .IllegalArgumentException Attempt to modify an object with no active transaction when NontransactionalWrite is disabled

Persist & remove in same transaction

I have a test case (attached) which performs the following actions: Open a new transaction Create & persist a simple entity object, EntityManager is flushed, Transaction is not committed Count ... Remove the entity object, EntityManager is flushed & cleared, Transaction is not committed Count

Error in production. Failed to commit transaction: Unexpected database state: BTree -152 is not found

.Read .doGet (115 ): Failed to commit transaction : Unexpected database state: BTree -152 is not found [ObjectDB 2.5.5] javax.persistence.RollbackException Failed to commit transaction : Unexpected

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 ... " [ObjectDB 2.6.9] javax.persistence.RollbackException Failed to commit transaction : Failed to set numeric

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

jakarta.persistence.FlushModeType

within a transaction , if AUTO is set on the Query or TypedQuery object, or if the flush mode setting ... is unspecified. If there is no transaction active or the persistence context is not joined to the current transaction , the persistence provider must not flush to the database. See Also: EntityManager

jakarta.persistence.SynchronizationType

with the current transaction or whether the persistence context must be explicitly joined to the current transaction by means of the EntityManager.joinTransaction method. Since: Jakarta Persistence (JPA) 2.1 ... transaction Since: Jakarta Persistence (JPA) 1.0 UNSYNCHRONIZED Persistence context must be explicitly

jakarta.persistence.PersistenceConfiguration

) Specify the transaction type for the persistence unit. Parameters: transactionType - the transaction ... transactionType () The transaction type . If PersistenceUnitTransactionType.JTA , a JTA data source ... may be provided via nonJtaDataSource . Returns: the transaction type. Since: Jakarta Persistence (JPA

jakarta.persistence.PersistenceContextType

, Comparable , Serializable Specifies whether a transaction -scoped or extended persistence context is to be used in PersistenceContext . If not specified, a transaction -scoped persistence context is used ... Persistence (JPA) 1.0 TRANSACTION Transaction -scoped persistence context Since: Jakarta Persistence

jakarta.persistence.PersistenceContext

PersistenceContextType type (Optional) Specifies whether a transaction -scoped persistence context or an extended persistence context is to be used. Default: PersistenceContextType. TRANSACTION ... whether the persistence context is always automatically synchronized with the current transaction or

Threaded Test - Failed to commit transaction: Unexpected internal exception

Threaded Test - Failed to commit transaction: Unexpected internal exception

jakarta.persistence.EntityManager.refresh(Object,LockModeType)

: the PessimisticLockException is thrown if the database locking failure causes transaction -level ... : PessimisticLockException - if pessimistic locking fails and the transaction is rolled back. LockTimeoutException ... PersistenceContextType. TRANSACTION when there is no transaction ; if invoked on an extended entity manager

jakarta.persistence.EntityManager.refresh(Object,LockModeType,Map)

is thrown if the database locking failure causes transaction -level rollback the LockTimeoutException ... : PessimisticLockException - if pessimistic locking fails and the transaction is rolled back. LockTimeoutException ... . TRANSACTION when there is no transaction ; if invoked on an extended entity manager

jakarta.persistence.EntityManager.refresh(Object,RefreshOption...)

: the PessimisticLockException is thrown if the database locking failure causes transaction -level rollback ... - if pessimistic locking fails and the transaction is rolled back. LockTimeoutException ... . TRANSACTION when there is no transaction ; if invoked on an extended entity manager

jakarta.persistence.TypedQuery.getResultStream()

and the transaction is rolled back. LockTimeoutException - if pessimistic locking fails ... and the transaction is rolled back. TransactionRequiredException - if a lock mode other than NONE has been set and there is no transaction or the persistence context has not been joined

jakarta.persistence.TypedQuery.getSingleResult()

fails and the transaction is rolled back. NoResultException - if there is no result. PersistenceException - if the query execution exceeds the query timeout value set and the transaction is rolled ... and there is no transaction or the persistence context has not been joined to the transaction . Since: Jakarta Persistence (JPA) 1.0

jakarta.persistence.TypedQuery.getSingleResultOrNull()

back. PessimisticLockException - if pessimistic locking fails and the transaction is rolled back. PersistenceException - if the query execution exceeds the query timeout value set and the transaction is rolled ... and there is no transaction or the persistence context has not been joined to the transaction . Since: Jakarta Persistence (JPA) 3.2

jakarta.persistence.TypedQuery.getResultList()

- if pessimistic locking fails and the transaction is rolled back. LockTimeoutException - if pessimistic locking ... the query timeout value set and the transaction is rolled back. TransactionRequiredException - if a lock mode other than NONE has been set and there is no transaction or the persistence context has not

jakarta.persistence.EntityManager.joinTransaction()

() Indicate to the entity manager that a JTA transaction is active and join the persistence context ... the scope of the active transaction or on an entity manager of type SynchronizationType.UNSYNCHRONIZED to associate it with the current JTA transaction . Throws: TransactionRequiredException

jakarta.persistence.EntityManager.runWithConnection(ConnectionConsumer)

with a transaction , the action is executed in the context of the transaction . The given action should close ... back the transaction . If the given action throws an exception, the persistence provider must mark the transaction for rollback. Parameters: action - the action Throws: PersistenceException - wrapping the checked