Minor Description
Improve the text associated with ERROR XSDB3: Container information cannot change once written: was 103, now 80. It would be nice to know which
database and container at least, and possibly any other info that may have changed. Maybe page/hex dumps to track down overlapping I/O errors on page 0.
Here is a stack trace reported as part of DERBY-3607, as encountered by a back ground thread:
2008-06-12 08:53:12.421 GMT Thread[derby.rawStoreDaemon,5,derby.daemons] Cleanup action starting^M
ERROR XSDB3: Container information cannot change once written: was 103, now 80^M
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)^M
at org.apache.derby.impl.store.raw.data.AllocPage.WriteContainerInfo(Unknown Source)^M
at org.apache.derby.impl.store.raw.data.FileContainer.writeHeader(Unknown Source)^M
at org.apache.derby.impl.store.raw.data.RAFContainer.writeRAFHeader(Unknown Source)^M
at org.apache.derby.impl.store.raw.data.RAFContainer.clean(Unknown Source)^M
at org.apache.derby.impl.services.cache.ConcurrentCache.cleanAndUnkeepEntry(Unknown Source)^M
at org.apache.derby.impl.services.cache.ConcurrentCache.cleanEntry(Unknown Source)^M
at org.apache.derby.impl.services.cache.BackgroundCleaner.performWork(Unknown Source)^M
at org.apache.derby.impl.services.daemon.BasicDaemon.serviceClient(Unknown Source)^M
at org.apache.derby.impl.services.daemon.BasicDaemon.work(Unknown Source)^M
at org.apache.derby.impl.services.daemon.BasicDaemon.run(Unknown Source)^M
at java.lang.Thread.run(Unknown Source)^M