153 words

recovery enabled="false", still creates tablename.odb$ files

2016-04-18 18:28

Running in embedded mode, configuration specifies "<recovery enabled ="false"... />".  Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly.


What do we need to do to not utilize recovery files (not have orphan tablename.odb$ files)?

kevinwh's picture
Joined on 2012-11-07
User Post #11
2016-04-18 18:33

Could you please verify that this setting is in the correct objectdb.conf file?

As explained on this page (with more details):

The value of $objectdb (the ObjectDB home directory) is derived from the location of the objectdb.jar file. It is defined as the path to the directory in which objectdb.jar is located, with one exception - if the name of that directory is bin, lib or build the parent directory is considered to be the ObjectDB home directory ($objectdb).

... by default the configuration file is loaded from $objectdb/objectdb.conf.

You can add an XML error to the objectdb.conf file. If your application is still running then it is not the right file.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support's picture
Joined on 2010-05-03
User Post #2,494

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Maximum file size: 32 MB