ObjectDB ObjectDB

Internal Website Search

21-30 of 116 resultsRefresh

Out of memory

on cold database now finish in 300ms: 2012-09-20 11:15:19.139 [http-bio-8080-exec-3] DEBUG o.s.b.f ... -exec-3] DEBUG p.h.p.inspiration.InspirationIndex - Before getting maps... 2012-09-20 11:15:20.021 ... -8080-exec-3] DEBUG p.h.p.inspiration.InspirationIndex - After product demands map... 2012-09-20 11:15

EntityManager.find(entityClass, primaryKey) is slow when accessing non-existent IDs

Is this problem solvable? --- package debug; import static java.lang.System.out; import ... (" " + d + "\t" + order.get(d)); } } --- 11:00:49.520 [main] DEBUG org.jboss.logging ... the classpath 11:00:49.562 [main] DEBUG org.hibernate.jpa.HibernatePersistenceProvider - Located

ODB IndexActivation NullPointerException

) {         log.debug("Thread interruped during join the 'ODB-IndexActivation' thread");     } } em ... ();     } catch (InterruptedException e) {         log.debug("Thread interruped during join the 'ODB-IndexActivation' thread");     } } else {     log.debug("Thread ODB IndexActivation not

ClassCastException of same object type

"ICoreObject". The source code is attached. When I debug, the object is retreived but when I try ... ; } When the query is run, debugging shows that "list" contains the XCCompetitorCount objects I persisted earlier ... ico : list){ cop.add(ico); } then debugging moves past that line and fails in the cop.add() method

Error using query with MAX() function

how to narrow this one down. How do you debug the cause of internal errors other than setting log level to debug and getting the stack trace? Here is my log output at the time of the error with log level set to debug. [2011-05-02 21:10:36 #150 query.manager] <queryRequest query="SELECT MAX($1.addDate

Join query problem with new statetment

: 2011-07-05 06:40:34.781 ["http-bio-8080"-exec-3] DEBUG p.h.dao.impl.InspirationDAOImpl - getPerSupplier. supplier id: 52 2011-07-05 06:40:34.847 ["http-bio-8080"-exec-3] DEBUG o.s.orm.jpa ... .847 ["http-bio-8080"-exec-3] DEBUG o.s.orm.jpa.JpaTransactionManager - Should roll back transaction

InternalError on multiple AND and JOIN Query

.action.ConfigurationAction - debug attribute not set 09:30:08,828 |-INFO in ch.qos.logback.core.joran ... ch.qos.logback.classic.joran.action.LevelAction - com.contextspace level set to DEBUG 09:30:08,928 ... - Attaching appender named [SIZE_BASED_ROLLING_APPENDER] to Logger[ROOT] <<TRIMMED DEBUG OUTPUT>>> Tests run

2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object"

again with ObjectDB logging "debug" to see if there is some class loading failure for SingleFieldIdentity ... that we didn't see because I used "info" and not "debug" in the ObjectDB log?". If you tell me #11 ... trace in #11 is normal in debug. support Support Switching from "StringIdentity" to "String" resolves

Unexpected internal exception during set field of an Embeddable to null

and debugging I hope that I found a important hint. The stack trace has been reduced to very (by the printer ... SignalValueImpl, decompiled it and debugged the decompiled SignalValueImpl. And beforeModifyMember ... Support We have tried to create a testCase. But it is not so easy to debug it. We have a long

Freeze during save

or maybe enable remote debugging? support Support I can reproduce the problem with remote debugging ... idea how to change this test case to reproduce the exception? Debug logging was added in version 2.7 ... with <logger name="entity.persist.cascade" level="debug" /> and post the relevant log lines? Thanks

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