Issue #800: Unexpected Internal Exception

Type: Bug ReoprtVersion: 2.4.0Priority: NormalStatus: ClosedReplies: 2
#1

Just got this:

13:09:11,309 SCHWERWIEGEND [com.quasado.galaxy.api.servlet.UIApplication] (http--127.0.0.1-8080-7) Critical error:: com.objectdb.o.InternalException: Unexpected internal exception
at com.objectdb.o.JPE.h(JPE.java:165) [objectdb-2.4.0.jar:]
at com.objectdb.o.ERR.f(ERR.java:70) [objectdb-2.4.0.jar:]
at com.objectdb.o.OBC.onObjectDBError(OBC.java:1504) [objectdb-2.4.0.jar:]
at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:695) [objectdb-2.4.0.jar:]
[snip]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
Caused by: java.lang.NullPointerException
at com.objectdb.o.WVP.q(WVP.java:539) [objectdb-2.4.0.jar:]
at com.objectdb.o.WVP.p(WVP.java:506) [objectdb-2.4.0.jar:]
at com.objectdb.o.WVP.o(WVP.java:392) [objectdb-2.4.0.jar:]
at com.objectdb.o.WVP.n(WVP.java:354) [objectdb-2.4.0.jar:]
at com.objectdb.o.WVP.m(WVP.java:236) [objectdb-2.4.0.jar:]
at com.objectdb.o.WVP.j(WVP.java:158) [objectdb-2.4.0.jar:]
at com.objectdb.o.WHP.j(WHP.java:345) [objectdb-2.4.0.jar:]
at com.objectdb.o.WHP.h(WHP.java:252) [objectdb-2.4.0.jar:]
at com.objectdb.o.WHP.g(WHP.java:185) [objectdb-2.4.0.jar:]
at com.objectdb.o.WHP.g(WHP.java:121) [objectdb-2.4.0.jar:]
at com.objectdb.o.QPN.d(QPN.java:86) [objectdb-2.4.0.jar:]
at com.objectdb.o.QRC.u(QRC.java:188) [objectdb-2.4.0.jar:]
at com.objectdb.o.QRM.U5(QRM.java:248) [objectdb-2.4.0.jar:]
at com.objectdb.o.MST.U5(MST.java:953) [objectdb-2.4.0.jar:]
at com.objectdb.o.WRA.U5(WRA.java:290) [objectdb-2.4.0.jar:]
at com.objectdb.o.WSM.U5(WSM.java:113) [objectdb-2.4.0.jar:]
at com.objectdb.o.STC.r(STC.java:447) [objectdb-2.4.0.jar:]
at com.objectdb.o.SHN.aj(SHN.java:489) [objectdb-2.4.0.jar:]
at com.objectdb.o.SHN.K(SHN.java:156) [objectdb-2.4.0.jar:]
at com.objectdb.o.HND.run(HND.java:133) [objectdb-2.4.0.jar:]
... 1 more
#2

Can you demonstrate the exception by providing a database and a query?

ObjectDB Support
#3

This issue is closed due to inability to reproduce the problem.

It should be reopened if new information becomes available.

ObjectDB Support

Reply