ObjectDB Database Search

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

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

unlimited debugging services. Please understand that it doesn't matter for ObjectDB if you store an empty

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

= result.get(0); logger. debug ("[trace_fetch] ["+g.getMembers().size()+"]"); return g; } } finally { em

Hello! Today i upgraded to 2.3.5_04. My program stopped working. After some debugging i found out that all fields of retrieved objects are on their default value till i first call a getter or detach them explicitly. Up to 2.3.4 they where initialized immediately. The problem in my case is that i

.isDebugEnabled()) {     codeLogger. debug ("Created a new PM ("+pm+")"); } try {  

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

debug thru the controller class.   Thanks siegfried siegfried siegfried heintze I am not sure I

Hi, Using 2.4.6_01 version on Linux (2.6.18, VPS)..  Just wondering what should I suppose to see in a log file with a log level 'trace'/' debug '.. Trying to fix an issue that server version sometimes accidentally quits without any notice.. My log file (independently on whats specified in

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

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

to the configuration file: or, use the " debug " level to get more information on the registered type

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

; It seems like this error somehow changes our logging level to DEBUG . Is there possibility that ObjectDB's

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

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

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

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

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

Hello, we still have memory usage problems. When debugging , we have now observed a case in which the execution of multiple queries increasingly byte array were generated (about 1.5 GB) which from GC could not be released. Not even after the EntityManagerFactory closed. We created a small test

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

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

of the real problem.) Similarly, using debug logging can also trigger loading.  

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

is attached. I also attached screenshots from the debug enviroment showing the values of the variables in

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

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

(" debug " level).  The "Works_xxx" file is from the build computer that has no error.  The "Fails

is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING to avoid

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

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

. Would you please explain how I can use the tracing information to debug

while debugging , but after a fresh selection of the previously changed object, the old values

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

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

license. Is there some way to debug this? Alternatively is there some docker configuration

, since the last breakpoint (i.e. an available db backup), e.g. for debugging . In replication

for the fields in the query. Log of the query execution using DEBUG logging level. support Support Hello

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

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

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

I have a problem loading lazy associations by access/navigation with an @Embedded attribute containing an @ElementCollection which is lazy loaded.  I'm not sure if the same problem exists elsewhere.  Furthermore, if I set a breakpoint in the right spot in debug mode, everything works

(Main.java:49) While debugging I noticed that unexpectedly for me both root and joinParent

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

Improved recovery from failure when recovery is enabled with no sync  ( issue #2293 ). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading ( issue #2299 ). Fixed a bug in restricting server access to a range of IPs ( issue #2292 ). Fixed

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

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

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

if that still affects it.  Or if there is something I can log in the debug to output