ObjectDB ObjectDB

Internal Website Search

31-40 of 200 resultsRefresh

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 (domain.Pronostikoa:72) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:289) at test.dataAccess ... , and at the commit clause it throws the exception. If you could explain to me why is it happening i

finding post-persist pre-commit objects

Hi, I'm wondering if there is a way to have post-persisted, pre-committed, objects show up in queries? ie: the object has been persisted, but not yet committed. Dave dmoshal David Moshal Yes, by setting the flush mode. support Support thanks, worked for me. dmoshal David Moshal

Query problem after transaction commit

.begin ... persist(p) .. commit of a new object, my client program can no longer retrieve the old ... issue with a simple solution (e.g. changing flush mode from commit to auto could solve

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 ... (and commit) after emptying its string fields? support Support If you use a deep nested embedded objects in

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 ... .onObjectDBError(OBC.java:1493) ~[OBC.class:na] at com.objectdb.jpa.EMImpl.commit(EMImpl.java:279

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

Need to close+open database for a commit to be taken into account

Hi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open but it does not work. So currently there is a dirty close + open + reload on each update

Query and commit simultaneously

Is it possible to query and commit on the same persistence manager (i.e. same odb file) at the same time? jake Jake Hang Multithreading is fully supported by ObjectDB, so you can query and update the database at the same time using multiple threads. However, if all the threads share the same

StackOverflowError after commit

We have following issue, if we execute a commit: java.lang.StackOverflowError at com.objectdb.o.ENT.D(ENT.java:411) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:417) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D

Error on commit

I get the following on commit: (v2.3.7_15) Let me know if you need more info. Caused by: com.objectdb.o.InternalException at com.objectdb.o.InternalException.f(InternalException.java:236) [:] at com.objectdb.o.SPW.aq(SPW.java:109) [:] at com.objectdb.o.PGW.am(PGW.java:210) [:] at com.objectdb

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