Issue #1142: Exception Failed to read from file

Type: Bug ReoprtVersion: 2.5.0Priority: HighStatus: ClosedReplies: 1
#1

Hello,

we have found several these exceptions in our log

[ObjectDB 2.5.0_06] javax.persistence.PersistenceException
Failed to read from file 'C:\SafeQORS\server\cache\MainORSCache.odb' (error 117)
at com.objectdb.jpa.EMImpl.find(EMImpl.java:596)
at com.objectdb.jpa.EMImpl.find(EMImpl.java:514)
at com.ysoft.cache.objectdb.ObjectCacheDB.deleteInOpenTransaction(ObjectCacheDB.java:361)
at com.ysoft.cache.objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:356)
at com.ysoft.cache.objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:347)
at eu.ysoft.safeq.ors.CacheDBWrapper.delete(CacheDBWrapper.java:73)
at ysoft.sqcore.job.CacheJobManager.jobExtinction(CacheJobManager.java:512)
at ysoft.sqpro.queue.PrintQueue.deleteJobOnSafe(PrintQueue.java:2124)
at ysoft.sqpro.queue.PrintQueue.processJob(PrintQueue.java:1432)
at ysoft.sqpro.queue.SecuredPrintQue.singleDeviceQue(SecuredPrintQue.java:499)
at ysoft.sqpro.queue.SecuredPrintQue.run(SecuredPrintQue.java:350)
Caused by: com.objectdb.o.UserException: Failed to read from file 'C:\SafeQORS\server\cache\MainORSCache.odb'
at com.objectdb.o.MSG.d(MSG.java:74)
at com.objectdb.o.LFL.U(LFL.java:1077)
at com.objectdb.o.PAG.an(PAG.java:841)
at com.objectdb.o.PGC.w(PGC.java:238)
at com.objectdb.o.SNP.F(SNP.java:421)
at com.objectdb.o.MST.aU(MST.java:475)
at com.objectdb.o.MST.aT(MST.java:434)
at com.objectdb.o.MST.U3(MST.java:407)
at com.objectdb.o.WRA.U3(WRA.java:251)
at com.objectdb.o.LDR.F(LDR.java:532)
at com.objectdb.o.LDR.E(LDR.java:466)
at com.objectdb.o.LDR.z(LDR.java:268)
at com.objectdb.o.OBC.aO(OBC.java:1052)
at com.objectdb.o.OBC.aM(OBC.java:970)
at com.objectdb.jpa.EMImpl.find(EMImpl.java:591)
... 10 more
Caused by: java.io.EOFException
at java.io.RandomAccessFile.readFully(Unknown Source)
at com.objectdb.o.LFL.U(LFL.java:1072)

...

These exceptions are occurring regularly. What is the cause of this exception? Is there any workaround?

We need to finally run our application without futher problems.

Thanks

Marta

#2

This issue is closed as duplicate of issue #1137 (different but related exception).

ObjectDB Support

Reply