ObjectDB ObjectDB

Internal Website Search

51-60 of 99 resultsRefresh

Dirty checking

just drop the transaction? Don't I have to either rollback or commit it? Let's take a step ... at the end of any request. thoughts? dmoshal David Moshal OK. Rollback is fine, of course ... . Regarding rollback, the JPA state diagram seems to indicate that post commit entities

New to Product & Having An Issue

(); if(em.getTransaction().isActive()) em.getTransaction().rollback ... ().rollback(); assertTrue(false); } } @After public void ... (); if(em.getTransaction().isActive()) em.getTransaction().rollback

How to Use a SF with extended Persistence Context?

._TransactionRequiredException: Attempt to rollback a transaction when no transaction is active at com.objectdb.o.JPE.g(JPE ... .arjunacore.BaseTransaction.rollback(BaseTransaction.java:134) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) at org.jboss.as.ejb3.tx

Run out of memory

and store it back in the database to access / modify later. I require to be able to rollback changes ... onRollback() { this.em.getTransaction().rollback(); this.em.clear(); this.em.close();     System.err.println("Rollback Done"); } The general call of these functions are: onBegin

Memory Leak in EntityManagerFactory ?

with no commit or rollback). Possibly, this behaviour is to avoid cleaning objects that are still in ... / rollback any active transaction before closing an EntityManager, which is a good practice ... ().rollback(); } ... if (manager.isOpen()) {                    // Condition B try { manager

pesimistic Lock semantic

.currentTransaction().rollback(); System.out.println(Thread.currentThread().getName ... ()) pm1.currentTransaction().rollback(); pm1.close(); } if (pm2 != null) { if (pm2.currentTransaction().isActive()) pm2.currentTransaction().rollback(); pm2.close

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

.persistence.TransactionRequiredException Attempt to rollback a transaction when no transaction is active ... .persistence.TransactionRequiredException Attempt to rollback a transaction when no transaction ... .PersistenceException Attempt to rollback a transaction using a closed EntityManager (error 525) at com

Best practise loading big data

only. If it is a read only operation, do you really need commit? maybe you can use rollback or clear instead ... so we do not need to commit - commit is a NOOP. If it is faster to rollback or just to clear ... expect performance improvements with rollback / clear, although it makes more sense to use them and maybe


or rollback operation. Only one Synchronization instance can be registered with the Transaction


Method javax.jdo.Transaction void setRollbackOnly() Sets the rollback-only status of the transaction to true. After this flag is set to true, the transaction can no longer be committed, and any attempt to commit the transaction will throw JDOFatalDataStoreException. Since: JDO 2.0

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support