Issue #565: Exception on the recovery of a database

I've had this exception on the recovery of a database:

[2011-11-06 04:33:41 #19 store]
Exception during recovery of 'F:\calculationservice\objectdb\dbs\admin\WorkflowHistoryArchive.odb': java.lang.ArrayIndexOutOfBoundsException
at java.util.zip.CRC32.update(CRC32.java:43)
at com.objectdb.o.PAG.an(PAG.java:860)
at com.objectdb.o.SFL.J(SFL.java:519)
at com.objectdb.o.SFL.I(SFL.java:442)
at com.objectdb.o.SFL.<init>(SFL.java:252)
at com.objectdb.o.MST.<init>(MST.java:109)
at com.objectdb.o.MST.aH(MST.java:94)
at com.objectdb.o.MSF.UI(MSF.java:178)
at com.objectdb.o.OMF.am(OMF.java:746)
at com.objectdb.jpa.EMF.am(EMF.java:156)
at com.objectdb.o.OMF.al(OMF.java:692)
at com.objectdb.jpa.EMF.createEntityManager(EMF.java:173)
at rbccm.felix.gridservice.admin.dao.ConnectionManagerFactory.createEntityManager(Unknown Source)
at rbccm.felix.gridservice.admin.dao.HistoryArchiver.populateArchive(Unknown Source)
at rbccm.felix.gridservice.admin.dao.HistoryArchiver.moveHistory(Unknown Source)
at rbccm.felix.gridservice.admin.dao.HistoryArchiver.access$400(Unknown Source)
at rbccm.felix.gridservice.admin.dao.HistoryArchiver$1.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)

This may reflect a normal situation in which the last record in the recovery file is incomplete. In that case the last record is ignored (since it represents a transaction that has not been completed). But maybe the output should be changed.

After this recovery - did you have any problems with the database? Can you check it with the Doctor?

Ok, sounds reasonable. No - there were no problems with the database after recovery but I thought it was worth checking the cause of the exception.

Sure. Such reports are always useful.

I see that the exception is written to the log with a WARING level.

It would be changed to TRACE in the next build (2.3.3_01).