Jira is down but I just wanted to post my findings regarding this patch.
On z/OS I got through 200 clean iterations of the original
reproduction. On Windows I ran ReproCorruptionBackgroundCheckpoint with
IBM 1.6. On the 170th run I got the EOFException that I reported earlier.
============= begin nested exception, level (4) ===========
java.io.EOFException
at java.io.RandomAccessFile.readInt(RandomAccessFile.java:739)
at
org.apache.derby.impl.store.raw.log.LogToFile.verifyLogFormat(Unknown
Source)
at
org.apache.derby.impl.store.raw.log.LogToFile.getLogFileAtPosition(Unknown
Source)
at
org.apache.derby.impl.store.raw.log.LogToFile.getLogFileAtBeginning(Unknown
Source)
at
org.apache.derby.impl.store.raw.log.Scan.getNextRecordForward(Unknown
Source)
at org.apache.derby.impl.store.raw.log.Scan.getNextRecord(Unknown
Source)
at org.apache.derby.impl.store.raw.log.FileLogger.redo(Unknown Source)
at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown Source)
at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
Source)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
Source)
at
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
Source)
at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
Source)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
Source)
at
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
Source)
at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
Source)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(Unknown
Source)
at
org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:316)
at java.sql.DriverManager.getConnection(DriverManager.java:273)
at CheckTables.main(CheckTables.java:8)
============= end nested exception, level (4) ===========
Cleanup action completed
My conclusion is that the patch does indeed fix DERBY-4239 an the
EOFException is a different issue, but one that happens less frequently
with the patch. I will file a new issue for that when Jira is back up.
Thanks
Kathey
