ObjectDB ObjectDB

Internal Website Search

101-110 of 116 resultsRefresh

Need help to analyse very high memory usage by objectdb (PRU, SEV, VAL[])

Hello, we have a useCase in which we consume too much memory and run into a "GC overhead limit exceeded" exception. Nearly 90% of the memory are taken by com.objectdb.o.PRU (49%) com.objectdb.o.SEV (29%) and com.objectdb.oVAL [] (9%). When debugging, we did not get the reason for the high memory

can removing an entity throw an exception if the entity is in use?

reports broken references so it could be very helpful during testing and debugging in identifying

High memory consumption even after close() of EntityManagerFactory

Hello, we still have memory usage problems. When debugging, we have now observed a case in which the execution of multiple queries increasingly byte array were generated (about 1.5 GB) which from GC could not be released. Not even after the EntityManagerFactory closed. We created a small test

Pre-detach loading: retrieval by navigation not working in if statement

of it, preventing discovery of the real problem.) Similarly, using debug logging can also trigger loading

Eager Fetch is not stable for collection or map types?

).getResultList(); if(result.size() > 0) { Game g = result.get(0); logger.debug("[trace

NegativeArraySizeException on commiting a transaction

is attached. I also attached screenshots from the debug enviroment showing the values of the variables in

Log4j error

this error somehow changes our logging level to DEBUG. Is there possibility that ObjectDB's logging

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

class diagram of @Startup collaboration in latest test web app: The full debug logging

ObjectDB 2.8.7

Added an option to slow backup (see feature request #2681). Added an option to view old type versions in the Explorer (-Dobjectdb.ui.debug=true) Improved the Doctor (see issue #2691). Improved performance following a large eager fetch (issue #2694). Restricted waiting time on closing a database

ClassCastException in Tuple.get

:   Main$EntityChild cannot be cast to Main$EntityClass at Main.main(Main.java:49) While debugging

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