ObjectDB ObjectDB

Internal Website Search

141-150 of 200 resultsRefresh

pesimistic Lock semantic

that lock could not be granted, quite nice but in that moment I wanted commit the first transaction and I ... ().commit(); } catch (JDOUserException e1) { pm1.currentTransaction().commit(); pm2 ... () + " --" + "Pesimistic lock succed"); return; } pm1.currentTransaction().commit

Error using query with MAX() function

.setChangeDate(new Date(System.currentTimeMillis())); em.getTransaction().commit(); em ... = (Date)tq.getSingleResult(); em.getTransaction().commit(); System.out.println("MaxDate ... . Hawks There seems to be a link between how often I commit and the results of success or failure. If I

Mysterious "Attempt to persist a reference to a non managed instance" error

exceptions at commit time. I've stripped it down to a set of files that seem to be of trivial complexity ... );       em.persist(oo);         tx.commit();     } } I had started with the expectation ... .RollbackException Failed to commit transaction: Attempt to persist a reference to a non managed failing


")) transaction.commit() } @Entity class Address{ String street } Fantom using [java] javax.persistence ... {street = "Fantom"}) getTransaction.commit } } } @Entity class Address{ Str? street ... .o._RollbackException: Failed to commit transaction: Failed to get reference value of field field

Different behavior with persist() and queried instances?

persist works though in a sample project, *after* the commit, my list property is correctly enhanced ... : After the commit and persist calls I do close the entity manager so my object gets detached. Between the persist() and the commit() call, my list property seems to be correctly tracked as it includes

Error 613 - i cant put a list<Athlete> into a Squad object

.RollbackException Failed to commit transaction: Failed to write the value of field test.Squad ... 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:259) at test.Main.main(Main.java:25) Caused by ... ) at com.objectdb.o.OBM.bD(OBM.java:711) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:256) ... 1

Eclipse plugin problem (using ObjectDB as a separate bundle)

.EMImpl.commit(EMImpl.java:277) at javax.jdo.Transaction$commit.call(Unknown Source) at org.codehaus ... the problem. I noticed that the third line in the stack trace at com.objectdb.jpa.EMImpl.commit ... . Please try changing the configuration: <cascade-persist always="true" on-persist="false" on-commit

Use temporary files to enable very large transactions

We managed to add a new option of using temporary files for flush / commit, as suggested in #6 ... of this database. This enables us to repeatedly commit on the second database and in case of a fault we can still recover a consistent state. We run the commit, if the Application consumes a percentage

InternalException during producer/consumer scenario

) Caused by: com.objectdb.o._RollbackException: Failed to commit transaction: Unexpected internal exception ... .onObjectDBError(OBC.java:1386) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:259) at rbccm.felix ... .java:711) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:256) ... 4 more Caused by: java.lang

Server out of memory exceptions

an embedded database: [ObjectDB 2.2.8] javax.persistence.RollbackException Failed to commit transaction: Attempt to commit a transaction after failure in writing to database file 'F:\calculationservice\objectdb\dbs\admin\WorkflowHistory.odb' (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277

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