8 | Trouble viewing db in Explorer. the Doctor with no errors. -I have debug on, here is a sample of the console: [2012-06-07 11:08:06 #47186 ... related to the reported problem (it is written to the log file only when the logging level is DEBUG |
8 | 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 |
8 | 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 |
8 | 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 |
8 | Failed to commit transaction: Attempt to commit a rollback only transaction against the same database server. Essentially one client runs in debug mode in the ide, and has a breakpoint ... to the last ObjectDB build for both the client and the server. Enable debug level logging |
1 | 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 | 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 |
1 | ArrayIndexOutOfBoundException how can we help to solve the issue (debug...)? Thanks Marta Maruta M Sedlakova Assuming all the exceptions ... them? If we can see the exception in our debugging environment, we may be able to understand and fix |
1 | Strange Error with Criteria API and Sorting sense, there might not be any "$2" variable. More strangely, when debugging through the error doesn't error but if you run without debugging through then it happens. Please advise / fix |
1 | Negative snapshot user count exception to the database corruption. I've tried enabling a finer level (both 'trace' and 'debug') on the client side, but I'm not getting any new output. Any suggestions to help capture more useful debug |
