java.io.IOException: Illegal seek

#1

The Exception throws between whiles, is a bug? (ObjectDB 2.3.4_05)

[09:44:46.992] Caused by: com.objectdb.o.UserException: Failed to read from file '/home/app/resin/webapps/WEB-INF/objectdb/data.odb'
[09:44:46.992]  at com.objectdb.o.MSG.d(MSG.java:74)
[09:44:46.992]  at com.objectdb.o.LFL.T(LFL.java:1059)
[09:44:46.992]  at com.objectdb.o.PAG.am(PAG.java:818)
[09:44:46.992]  at com.objectdb.o.PGC.w(PGC.java:237)
[09:44:46.992]  at com.objectdb.o.SNP.B(SNP.java:366)
[09:44:46.992]  at com.objectdb.o.OBI.v(OBI.java:430)
[09:44:46.992]  at com.objectdb.o.OBI.s(OBI.java:339)
[09:44:46.992]  at com.objectdb.o.OBI.r(OBI.java:266)
[09:44:46.992]  at com.objectdb.o.PBI.q(PBI.java:94)
[09:44:46.992]  at com.objectdb.o.OBI.Vi(OBI.java:236)
[09:44:46.992]  at com.objectdb.o.BQI.Vr(BQI.java:144)
[09:44:46.992]  at com.objectdb.o.PRG.ag(PRG.java:734)
[09:44:46.992]  at com.objectdb.o.PRG.ae(PRG.java:663)
[09:44:46.992]  at com.objectdb.o.PRG.ad(PRG.java:539)
[09:44:46.992]  at com.objectdb.o.QRM.U4(QRM.java:259)
[09:44:46.992]  at com.objectdb.o.MST.U4(MST.java:947)
[09:44:46.992]  at com.objectdb.o.WRA.U4(WRA.java:290)
[09:44:46.992]  at com.objectdb.o.WSM.U4(WSM.java:113)
[09:44:46.992]  at com.objectdb.o.QRR.g(QRR.java:232)
[09:44:46.992]  at com.objectdb.o.QRR.b(QRR.java:151)
[09:44:46.992]  at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:666)
[09:44:46.992]  ... 19 more
[09:44:46.992] Caused by: java.io.IOException: Illegal seek
[09:44:46.992]  at java.io.RandomAccessFile.seek(Native Method)
[09:44:46.992]  at com.objectdb.o.LFL.W(LFL.java:1136)
[09:44:46.992]  at com.objectdb.o.LFL.T(LFL.java:1055)
[09:44:46.992]  ... 38 more
#2

It seems to be issue #621 that was fixed - please switch to build 2.3.6_14.

You may have to fix your database file by running the ObjectDB Doctor.

ObjectDB Support
#3

The problem still exists after updating to ObjectDB 2.3.6_14 and checking the db file by Doctor.

#4

Maybe the Doctor cannot fix this specific issue.

Try to use 2.3.6_14 with a new clean database and see if the problem still happens.

ObjectDB Support

Reply