ObjectDB ObjectDB

Internal Website Search

151-160 of 198 resultsRefresh
5

significant performance decrease

="write" /> <locking version-check="true" /> <processing cache="2048mb" max-threads="10
5

OutofMemory error with Object DB 2.0

="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10" /> <query
5

Updating Entities

._OptimisticLockException: Optimistic lock failed for object application.model.Paygrade#184 (object has version 86 instead
5

First query takes 4+ minutes to complete

="false" path="$objectdb/" mode="write" /> <locking version-check="true" /> <processing cache
5

FileNotFoundException

I'm sometimes getting this exception. Is there a simple answer to why it's occurring? (It could take some time to produce code that results in this exception reliably). Caused by: java.io.FileNotFoundException: /tmp/objectdb/tmp/objectdb_1252962966569709153/lock.lck (No such file or
5

Getting exception while executing the Query

I have facing a problem when i am executing the query first time, Please find the stack trace below java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301) at java.util.concurrent.Semaphore.acquire
1

ObjectDB 2.3.1

UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug (issue #520). Fixed
1

Best practise loading big data

that is somehow locked. Closing the entitiy manager should free the memory - but freeing no longer objects
1

Remove an entity which attributes were changed

We use an OSGi environment and we have three OSGi plugins. In plugin A an entity is loaded and the entity is passed to plugin B. Plugin B changes an attribute on the entity. Plugin C removes the entity from the database. After commit the transaction an exception is caused with optimistic lock
1

ObjectDB 2.2.1

Added support for using ObjectDB with JBoss AS 6.0 / 6.1. Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug. Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.

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