Home » Support » Issue Tracking » Internal exception

Internal exception

Type: BugVersion: 2.7.1Priority: CriticalStatus: ClosedReplies: 3
#1

Hello.

We got the following stacktrace.

Can you explain me what this internal exception means and why it was thrown?

It only happens when the entities are enhanced.

Best regards

BTC ES

 

com.objectdb.o.InternalException: Unexpected internal exception
at com.objectdb.o.ILP.iterator(ILP.java:169)
at com.objectdb.o.CLT.visitRefs(CLT.java:166)
at com.objectdb.o.TVS.j(TVS.java:169)
at com.objectdb.o.TVS.cascade(TVS.java:156)
at com.objectdb.o.STA.Q(STA.java:476)
at com.objectdb.o.STM.E(STM.java:408)
at com.objectdb.o.OBM.bQ(OBM.java:934)
at com.objectdb.jdo.PMImpl.bQ(PMImpl.java:2284)
at com.objectdb.o.OBM.bP(OBM.java:845)
at com.objectdb.o.OBM.bO(OBM.java:790)
at com.objectdb.o.QRR.f(QRR.java:139)
at com.objectdb.o.QRR.a(QRR.java:618)
at com.objectdb.o.InvMemberQuery.e(InvMemberQuery.java:139)
at com.objectdb.o.UMR.v(UMR.java:511)
at com.objectdb.o.ENT.loadInverse(ENT.java:1527)
at com.objectdb.o.IVP.m(IVP.java:149)
at com.objectdb.o.IVP.l(IVP.java:137)
at com.objectdb.o.ILP.iterator(ILP.java:168)

#2

The stack trace indicates an unexpected condition during attempt to resolve a mapped by relationship, which required a flush before running the mapped by query (due to changes since last commit/flush) in order to retrieve the mapped by instances. The stack trace indicates a failure to cascade persist operation from unknown reason during that flush.

Any more information could help. If you can find a more detailed exception stack trace in the log file it may also help.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3

Is there new information regarding this exception?

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#4

We have removed the 'mapped by' parameter of the relationship annotation. Now it works well.


Post Reply

To post a reply and/or subscribe to update notifications - please login