ObjectDB ObjectDB

Internal Website Search

71-80 of 152 resultsRefresh

SectionClassifier message in log

.framework.ApplicationException: Error flushing queue at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe.flush(Unknown Source) at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe.flush(Unknown

remove & persist in same transaction => Attempt to reuse an existing primary key value

); // If we call a FLUSH it works. // em.flush(); System.out.println("create and persist AGAIN"); // create ... id; } } A possible workaround, that this scenario works is to call a flush (see commet) after em

Performance in large transactions

to apply changes to the database on flush/commit. This could be done by keeping a copy of every managed object and comparing copies to actual objects on every flush or commit, but this is inefficient ... comparison on every flush. To avoid this, we introduce now a new method, con.objectdb.Utilities

Spring Transactions (@Transactional) within ObjectDB

Sandeep Sandeep Dhamale Build 2.5.2_01 adds support for enabling auto flush by default, by setting a system property:     System.setProperty("objectdb.temp.auto-flush", "true"); before loading ObjectDB, or as a JVM argument: > java -Dobjectdb.temp.auto-flush=true ... support Support

Heap Limit reached although the option 'objectdb.temp.page-file' is activated

although the flush and the GC were invoked regularly. The attachments show the memory heap dump ... .flush(OBM.java:765) ~[na:na] btc_es BTC EmbeddedSystems The heap dump shows millions of entity objects ... seem related to objectdb.temp.page-file, which may work and move modified database pages (after flush

Querys slower when execute a query after every persist

EmbeddedSystems When entity classes are not enhanced every flush or commit requires comparison ... and should be flushed to the database. If you have more objects in the current transaction it takes more time (i.e. every query execution requires a more expensive flush). Results of your test with enhanced

ObjectDB 2.2.6

Fixed the "Attempt to reuse an existing primary key value" after flush bug. Fixed a bug in tracking changes to collections of new flushed entity objects. Fixed generated value (ID allocation) bug with flush and in EJB containers. Fixed a NullPointerException on getObjectsById. Fixed a server freeze

docker documentation

>) piped.write(13) piped.flush() sleep(100) piped.println(<PASSWORD>) piped.write(13) piped.flush() sleep(100) piped.println(<LICENSE>) piped.write(13) piped.flush() } } Now here's the strange bit, the license url

Query in nested transaction returns detached entity if lazy-loaded

that have been persisted by other transactions from within a transaction that was flushed before these objects have been persisted. This is caused due to the way that currently ObjectDB manages flushed transactions as a snapshot of the database when flush occurs. Build 2.7.4_04 includes a workaround

stress test -> com.objectdb.o.InternalException: null

TestEntity());         em1.flush();                 EntityManager em2 = emf.createEntityManager ... as a result of running an UPDATE query on uncommitted flushed changes in some circumstances. A fix

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