Home » Search

About trace

101-110 of 200Refresh
Issue
1

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:

any part of the trace that reveals what inside com.greensoft.greenstar.ejb.ext ... ); // } return ok; }   The stack trace indicates an unexpected state of ObjectDB but doesn't
Forum
1

com.objectdb.o.NLV cannot be cast to com.objectdb.o.CMV

on how to avoid the exception? Thank you Emil     Same problem in 2.5.4_03. Please post the stack trace that you get with version 2.5.4_03. Here is the stack trace when using your DB explorer tool to run the query
Forum
1

Database Inconsistency or corruption

is currently executing. As an alternative, it would be nice to see the traces of all EntityManagers ... the database. If I had detailled traces of the EntityManager or of ObjectDB, I could identified
Forum
1

em.flush(); em.clear(); loosing data and not persisting managed objects

. Regarding the new internal exception - could you please attach the stack trace? Updating note d60/0/0 ... it seems that the stack trace will not be sufficient in this case. If and when you have time to generate a test case
Forum
1

Embedding ObjectDB on server application

? Here's the stack trace: (starting on 4th line is server app's trace) javax.persistence
Issue
1

Enhanced classes problem

, except the license check, which cannot cause this exception. The stack trace indicates an attempt to load ... the stack trace of that exception. We have checked our application with the ObjectDB (2.5.0_05
Issue
1

Error on commit

seems to be healthy. These stack traces are normal when using DEBUG level logging. As the result ... (Thread.java:662) ---------------------------------------------------------------- The stack trace
Forum
1

Error using query with MAX() function

report. I'm getting an error with as stack trace again on my DB and data. The test code above passes ... and getting the stack trace? Here is my log output at the time of the error with log level set
Issue
1

Exception in thread "ODB-StoreHandler-5094" java.lang.NullPointerException

, which writes them to it's log file.  The stack traces do show that the Exceptions are originating from ODB ... numbers in the stack trace do not match the most recent ObjectDB version.  Hi, The version of ODB
Forum
1

Failed to commit transaction: Attempt to commit a rollback only transaction

is the solution. In addition - the complete stack trace from the server log could help. ok ... . Try to reproduce the exception. Check the client and server log files for errors and exception stack traces. dmoshal