ObjectDB Database Search

... all work fine.   DB Doctor does not fix the problem. We need guidance on how to debug

object" session.rollback() is somehow causing the problem (found through debugging

for the version at run-time ? It does not seem to be in the odb logs, and turning on the debug mode does not

you debug this issue?   lwalkowski Lukasz Walkowski Please try build 2.2.8_09 that should fix

we cannot offer this service of debugging and investigating issues in user projects (obviously as

? Can you run ObjectDB on the same computer otherwise? support Support I'm now debugging , so two database

getSequence() returns null. I've tried increasing the logging level to " debug " in objectdb.conf

); }     return dtoList; }   1. What can we do to enable debugging /profiling

additional action (such as evict). support Support hi I've checked in debuger that every data model class

Hi! We need  the ObjectDB version for debug purpose/logging. Our project supports also EclipseLink - http://stackoverflow.com/questions/3493495/getting-database-connection-in-pure-jpa-setup With the Connection object the Database name & version can be retrieved. For ObjectDB

that out for sanity purposes with a debug statement.    Code: package com.objectdb.forum

the "index" logger to " debug " level. support Support The issue occurs yet with the version 2.8.5_05

_odbHidden. All fields have an _odbHidden partner. Is this a debug code leftover? Thank you Emil

for feedback, Webel   webel Dr Darren Kelly With logging enabled in debug level - some 'normal' 

and needed a lot of time for debugging and fixing). This is the error I got after adding a new field

this changed example, the exception is only caused in our OSGi example. I believe you must debug the OSGi

William I keep thinking this to myself and just based on some debugging I came to the assumptions

Hi, If I put the .jar into /opt/Tomcat/lib/, then where the .conf should be in? And the .odb? When I debug the Eclipse web project, I export all things into a .war file. Then I use Tomcat's web deploy tool by the .war file. However, if I put objectdb into the project's /WEB-INF/, I may lost the db

of this message may change from WARNING to DEBUG in the future. support Support I understand. Thank you. zmirc Mircea Chirac

without any error. Here is the log file in DEBUG mode, but there is nothing special or detailed error

won't allow schema evolution. dmoshal David Moshal not sure how to debug your question re the server

() cause exceptions. Yes, you'd better to put it into manual, since "drop table" is often in debugging

.City); } In debug mode i see that the objects in List results are of type Object and not Stadium

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

this problem. There is no time for debugging . itsme Martin Petzold Unfortunately we cannot tell

debugging . It requires starting with a duplicate database that is later used to play

So when we enhance the Account class, no changes are saved to it. When it is reflection mode, everything works perfectly. In reflection mode, the objectdb log on debug mode refers to classes that have not existed for ages.  In enhancement mode, there are no exceptions. I can't figure

; Here is my debug scenario: I have an existing DB File that contains One single root MyStepBlockCollection

mechanism. We enabled full logging (logger name="*" level=" debug ") and logged to a file with limited

I don't know why this cast is made ... i haven't any BigInteger in my app. Well, debugging

; bmcalist.odb Brian The database seems to be healthy. These stack traces are normal when using DEBUG level

when it happens. A live debugging may be essential. Can you share your stress test? No source is needed, just

We encountered an issue with the logging mechanism. We enabled full logging (logger name="*" level=" debug ") and logged to a file with limited size. We did not configure a log-archive (log-archive path="" retain="0"). That caused an exception when the log file reached its size limit

on!?? Here's the stacktrace (copy+paste from debug output): com.objectdb.o.MSG.d(MSG.java:61) com.objectdb.o.PRG.af(PRG