Issue #1643: InternalException: null

Type: Bug ReoprtVersion: 2.6.1Priority: HighStatus: FixedReplies: 1


when I run my application where 10 threads are concurrently accessing ObjectDB (only reading) via using ExecutorService, then these 2 mistakes are coming rapidly:


Caused by: com.objectdb.o._JdoObjectNotFoundException: Entity is not found:
at com.objectdb.o.JDE.g(
at com.objectdb.o.ERR.f(
at com.objectdb.o.JDE.f(
at com.objectdb.o.OBC.onObjectDBError(
at com.objectdb.jdo.PMImpl.getObjectById(
at eu.extech.serverImpl.jdo.JDOConnection.objectById(



[ObjectDB 2.6.1_02] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_05 (on Mac OS X 10.9.5).
Please report this error on
com.objectdb.o.InternalException: null
at com.objectdb.o.InternalException.f(
at com.objectdb.o.LDR.F(
at com.objectdb.o.LDR.E(
at com.objectdb.o.OBC.UO(
at com.objectdb.o.ENT.d(
at com.objectdb.o.ENT.extractMap(
at Source)
at Source)
at eu.extech.quai.ProductStateAttributeStorage.restore(
at eu.extech.quai.ProductStateAttributeStorage.createBasicDatabaseObjectCopy(
at eu.extech.serverImpl.QuantServerImpl.retrieveProductStateAttributeStorageForProductID(
at eu.extech.serverImpl.QuantServerImpl.access$3(
at eu.extech.serverImpl.QuantServerImpl$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

Every worker thread has its own connection to the DB. 

When running the app without the multithreading, no errors are coming.


Build 2.6.1_05 includes an addition of a synchronized wrapper, which might have been missing in the context of your second reported stack trace. If it does't solve the issue, we may need a test case that demonstrates the exception.

ObjectDB Support