ObjectDB ObjectDB

Internal Website Search

61-70 of 136 resultsRefresh

Start ObjectDB inside java code.

activate those line of code now? i mean where do i put the <server> <connection port="6136" max="100 ... try something like : String [] test = new String[2] ; test[0] = "connection port=6136 max=100" ; test ... command or argument: connection port=6136 max=100 (error 531) Am not sure this is the right place

best practice for configuration settings

questions regarding the configuration entry: ... <processing cache="64mb" max-threads="10" synchronized="false" /> ... max-threads we have 16 processor cores and around 400 clients communicating ... cores the optimum could be around max-threads="16", but there are no strict rules and tuning

Doctor - high memory usage

have at least 2GB RAM, I don't think that running the Doctor with 512MB max heap size should be a problem ... max heap size (-Xmx512m) it works well with the default configuration - it took ~10 seconds to check the database and additional 20 seconds to rebuild a new database. With 256MB max heap size I got

Best practice: Database update/migration of embedded databases in products

{ String firstName; String familyName; String address; } DB1: [firstName=”Max”; familyName=”Mustermann”; address=”26135 Oldenburg”] V1.1: EntityPerson{ String name; String address; } DB2: [name=”Max ... : [name=”Max Mustermann”; zip=”26135”; city=”Oldenburg”] How can we load the Database DB1

ODB IndexActivation NullPointerException

' * Batch ended at MAX * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at '2LG' * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at MAX If MAX is the last, then it looks like

Replaying recorded requests...

" sync="false" path="." max="128mb" />     <recording enabled="false" sync="false" path="." mode="write" />     <processing cache="64mb" max-threads="10" />     <query-cache results="32mb" programs="500

Objectdb recovery

Hello, I have question regarding objectdb recovery when objectdb is not finished correctly (power outage). We are using following configuration: <recovery enabled="true" sync="false" path="." max ... ): <recovery enabled="true" sync="true" path="." max="128mb"/> This setting guarantees

Explorer in 2.3

if you have millions of objects. Currently the workaround is to use queries with max results limit. Viewing all the objects of a class without a query and max result limit is not a common feature in

Activation Issue

="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10

Failed to commit transaction: Attempt to commit a rollback only transaction

enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="false" /> <processing cache="64mb" max-threads="10

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