Home » Support » Issue Tracking » com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: 2

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

Type: BugVersion: 2.5.3Priority: NormalStatus: ActiveReplies: 2
#1

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: 2
java.lang.ArrayIndexOutOfBoundsException: 2
at com.objectdb.o.UTY.aG(UTY.java:1275)
at com.objectdb.o.ENH.b(ENH.java:102)
at com.objectdb.o.LDR.J(LDR.java:796)
at com.objectdb.o.LDR.UW(LDR.java:1023)
at com.objectdb.o.CST.ab(CST.java:478)
at com.objectdb.o.CST.U4(CST.java:414)
at com.objectdb.o.LDR.F(LDR.java:559)
at com.objectdb.o.LDR.E(LDR.java:466)
at com.objectdb.o.OBC.UJ(OBC.java:1073)
at com.objectdb.o.QRR.h(QRR.java:295)
at com.objectdb.o.QRR.f(QRR.java:178)
at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:686)

...

Maybe caused by network inactivity timeout? We are using the following configuration 

<network inactivity-timeout="3600" />

 

#2

This exception stack trace may indicate a mismatch of entity class versions between the client and the server, i.e, the server was updated to use a new class schema, which the client is unaware to yet.

The ObjectDB server must be restarted after a schema change.

Do you still get the error after restarting the server?

 

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

You are right. After I restarted the server the error didn't come up again. Thanks. Would be great if you could catch these kind of  exceptions where the data model between client and server is different and log a more meaningful error message because in our development systems this kind of error occurs pretty often. Thanks.


Post Reply

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