10 | ClassNotFoundException Stack Traces in the Log FileIf I turn the log level in objectdb.conf to debug I get a lot of ClassNotFoundException's (see example below). My question is, is there a way to avoid these exceptions? [2013-02-05 10:52:30 #399 ... It is the normal behavior when using debug level logging globally. But you can decrease logging level |
10 | EntityManager JPA or JDO impl and different behavior into the objects in debug I can get see that somewhere inside nativeEntityManagerFactory=com ... in eclipse. This should allow you to debug the test project with objectdb. In addition yesterday I |
10 | Failed to resize file - file system limitation error during execution of DB Doctor on a different file? Also, is there any additional debugging ... in ObjectDB or a corrupted database file. Therefore, you might be able to debug it externally |
10 | ODB lost?I'm new to ObjectDB. While debugging small programs in single-step mode in NetBeans, the ODB appears to get corrupted or lost if I don't invoke close on EntityManager. If I re-run my program ... simultaneously by different processes, which is common during debugging (when running the application |
10 | Enhancement Check: <logger name="type" level="debug" /> and the names of the classes will be written ... the log, when you use build 2.7.6_05 and <logger name="type" level="debug" /> is set in the correct |
2 | NullpointerException at a normal selectWhen I run the following code: EntityManager em = getEm(); Customer result = null; try { logger.debug("Ident: "+ident); result = em.createQuery("Select c from Customer c where c ... -exec-9] DEBUG s.t.c.o.OrganizationService - Ident: default Oct 14, 2014 9:08:49 AM org.apache |
2 | Weird issue with variable naming during debugging because when you check the value of a path (which calls toString()), your whole query goes wrong after debugging!! thanks for a fast fix, Alex quasado Alexander Adam Yes, toString |
2 | DB persist operation results are not available for another Thread/EntityManager immdiately a query. But there are not any results available. We debugged the problem. Thread B executes the query ... at a debug break point. We steps over the next statement which also executes the identical query |
2 | Issue with DISTINCT Select() of the CriteriaQuery doesn't contain any variable named $3!!! And even worse.. when debugging in eclipse which calls ... !! so after debugging the query returns useless.. but anyway, I can ignore this however the issue mentioned before |
1 | ObjectDB 2.8.6_05Added an option to view old type versions in the Explorer (-Dobjectdb.ui.debug=true) |
