111 words


2013-05-19 14:44

Trying to move a project from test into production phase, I have started to get internal exceptions when working on large data sets:

java.util.concurrent.ExecutionException: com.objectdb.o.InternalException: Unexpected internal exception


Caused by: com.objectdb.o.InternalException: Unexpected internal exception
        at com.objectdb.o.WSM.U6(WSM.java:118)
        at com.objectdb.o.QRR.g(QRR.java:244)
        at com.objectdb.o.QRR.f(QRR.java:153)
        at com.objectdb.jdo.JdoQuery.execute0(JdoQuery.java:811)
        at com.objectdb.jdo.JdoQuery.execute(JdoQuery.java:720)

I can imagine how frustrating such internal exceptions must be to sort out.  Is there any more information I can provide?

sjzlondon's picture
Joined on 2013-04-21
User Post #5
2013-05-19 15:12

Please check for a longer stack trace (including nested stack traces) in the log file.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support's picture
Joined on 2010-05-03
User Post #1,533

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Maximum file size: 32 MB