ObjectDB ObjectDB

Internal Website Search

101-109 of 109 resultsRefresh

ObjectDB is opening too many sockets

logging enabled: <logger name="server" level="debug" /> During sudden events of socket

First query takes 4+ minutes to complete

); }     return dtoList; } 1. What can we do to enable debugging/profiling information in the logs? 2

Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found

.agent" level="error" /> </general> The level of this message may change from WARNING to DEBUG in

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

em.flush(); em.clear(); loosing data and not persisting managed objects

) This is the last entries in the log with log level debug. awhawks Adam W. Hawks As far as

Query can't see recently persisted object

.setParameter("oid", oid); if ("-62e6083d:1612795a01c:-6e65".equals(oid)) { logger.debug

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

Error on commit

DEBUG level logging. As the result of the exception in #1 you should have in the log file lines

Memory leak in com.objectdb.o.CST

if there is something I can log in the debug to output the connection pool settings to confirm? Trianglehead

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