About recovery

release

2.2.3

... Changed default configuration (enabled recovery, disabled recording). Fixed a critical database ...

 
release

2.2.4

... Changed default configuration (enabled recovery, disabled recording). Fixed a critical database ...

 
forum_thread

internal object DB locking in an embedded multi threaded application

Hi, we are using Embeded objectDB 2.4.4_06 in a highly multithreaded concurrent manner and we have noticed a performance problem in our application that seems to be attributed to ObjectDb's internal locking. When profiling our app in JVisualVm we notice a large number of threads are blocked and when doing a threaddump we notice that they are all blocked in the same place: ... resize = "500mb" page = "2kb" /> <recovery enabled = "true" sync = "false" path = "." max ...

 
forum_thread

in-memory and on-disk support?

I've had a quick read through the features/FAQ and haven't been able to find a clear answer. I'm looking at replacing a setup of H2 where I have 40GB in-memory backed by 800GB on-disk, the 40GB in memory represents the first 40GB of the 800GB on-disk for super-fast recent entry searching, the records at the end continuously purge as the new ones come in(duplicate write, one to in-memory and one to on-disk). ... ObjectDB uses a single file (you can disable logging, recovery, etc. for the memory database) - file system overhead is minimal. ...

 
forum_thread

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. ... resize = "256kb" page = "2kb" /> <recovery enabled = "true" sync = "false" path = "." max ...

 
forum_thread

Crash due to memory problems

We had a crash of our system, log reports the following: ... ... or tune the ObjectDB configuration. If ObjectDB recovery is enabled then ObjectDB should recover automatically when it is ...

 
forum_thread

OutofMemory error with Object DB 2.0

Hi, I am getting the below OutOfMemoryError after I have migrated from objectdb 1.0 to 2.0 The application works with 256MB heap size with objectdb 1.0  But on 2.0 even with max heap size of 1024MB, I get this error. The application reads xml file of around 1GB and creates a new odb file and inserts 200 records at a time. ... file (also attached). I think I have disabled recovery which was enabled in default conf: <!-- ObjectDB ... resize = "256kb" page = "2kb" /> <recovery enabled = "false" sync = "false" path = "." max ...

 
manual

[ODB1] Chapter 5 - JDO Connections

The PersistenShows how to use database connections and transactions in JDO. ceManagerFactory interface represents a factory of database connections. Its main role is to provide PersistenceManager instances. The PersistenceManager interface represents a database connection. Every operation on a database requires a PersistenceManager instance. The Transaction interface represents a transaction on a database. Every operation that modifies the content of the database requires an active transaction.[toc hidden:1]... database is opened. This feature, which is called auto recovery , is not supported by the free edition of ObjectDB. To ensure ... be disabled - at least for the database file and the recovery temporary file. Consult your operating system documentation for ...

 
forum_thread

Degrading performance overtime

hi, We have an application that uses embedded odb database. We have configured odb to start at 50meg chunks and grow at 50 megs a time. as the files become larger between 1 and 2 gigs we start to see considerable degrade in performance caused internal objectdb locking: ... = "51200kb" page = "2kb" /> <recovery enabled = "true" sync = "false" path = "." max ...

 
release

2.0.5

... Fixed a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding an entity ...