About sync
Database Management Settings
Explains settings and performance tuning of the ObjectDB Java object database for JPA/JDO.... /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> <recording enabled = "false" sync = "false" path = "." mode = "write" /> ... element <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> When ...
setSynchronization(sync)
The user can specify a Synchronization instance to be notified on transaction completions.(Method of javax.jdo.Transaction)
Safe Settings
Hi, I am trying to set up ObjectDb in a safe way that allows turning the machine off while database transactions are running. I would like to test if things are really safe and if I don't get corrupted database files in any possible case. I found "recovery" and "recording" in the objectdb.conf file. Which one is safer to use? I suppose I should turn on sync="true", right? ... one is safer to use? I suppose I should turn on sync="true", right? I already tried playing with both configuration ... with the debugger and I put a breakpoint in FileDescriptor#sync(). It never got triggered with no setting that I could come up with. How ...
Activation Issue
Hi, We bought a site license the yesterday. I ran the activation class this morning. That generated the activation key. I took that key as per the instructions, added it to the objectdb.conf inside the jar, and everything was happy. (this was with 2.3.7). However after a reboot I'm now getting the evaluation license restriction message again at compile time (which was I was seeing before putting the activation key in objectdb.conf). I tried upgrading to 2.3.7_02 and updating objectdb.conf with the activation key, but get the same behaviour. ... /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> <recording enabled = "false" sync = "false" path = "." mode = "write" /> ...
Optimistic lock failed
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 has version 1 instead of 3) Could you please explain what this means, and what I can do about it. Thanks you, Carl ... /> <recovery enabled = "false" sync = "false" path = "." max = "100mb" /> <recording enabled = "true" sync = "false" path = "." mode = "write" /> ...
Replaying recorded requests...
Hi, I get the following when ODB starts in embedded mode: Replaying recorded requests... then I get something like 500 lines of recordset information. Here is the relevant part of the config file: Questions: 1) Why am I seeing this if I've set recording enabled to false? 2) I... /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> <recording enabled = "false" sync = "false" path = "." mode = "write" /> ...
Sort of very large objects - out of memory
The attached test is failing with an out of memory exception when running with -Xmx512m It performs the following actions: 1) Create 5 persist threads which create and persist a large object in a loop 100 times each 2) Create 5 get threads which read 100 objects each in a loop based on object creation time and priority The message size should be around 1mb so I think there should be around 11mb of "live" data in play at any time. The objectdb cache settings are low in the config - database section is below for reference. ... /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> <recording enabled = "false" sync = "false" path = "." mode = "write" /> ...
Connection is closed Caused by: java.io.EOFException
I am getting this exception on a regular basis, after a period of time of repeating the same code execution. I don't understand why. I restart the DB server and my code works again for another period of time until same exception is encountered again. I cannot pin down a pattern e.g. after a certain period of time, because the time periods between exceptions are not regular, although frequent. Any test case I use will pass most of the time but will fail after an undetermined period. ... /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> <recording enabled = "false" sync = "false" path = "." mode = "write" /> ...
javax.jdo.Transaction
The JDO Transaction interface provides for initiation and completion of transactions under user control.(Interface of JDO)
Failed to commit transaction: Attempt to commit a rollback only transaction
Anyone know what this means?? Suddenly cropped up. Failed to commit transaction: Attempt to commit a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source) ... page="2kb" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking ...
