databas threw an error
This is the first error. There are lots more. What does it mean?
!SESSION 2009-07-08 12:53:54.221 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_13 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY com.fnfr.foundation 4 4 2009-07-08 14:31:49.721 !MESSAGE Test Report Database task threw an exception: !STACK 0 java.util.concurrent.ExecutionException: java.sql.SQLException: Log Record has been sent to the stream, but it cannot be applied to the store (Object null). This may cause recovery problems also. at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at com.fnfr.foundation.database.Database$1.ffrun(Database.java:185) at com.fnfr.foundation.FanfareRunnable.run(FanfareRunnable.java:86) at java.lang.Thread.run(Unknown Source) Caused by: java.sql.SQLException: Log Record has been sent to the stream, but it cannot be applied to the store (Object null). This may cause recovery problems also. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source) at com.fnfr.svt.testreport.database.TestReportDatabase$35.call(TestReportDatabase.java:1024) at com.fnfr.svt.testreport.database.TestReportDatabase$35.call(TestReportDatabase.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at com.fnfr.foundation.database.Database$1.ffrun(Database.java:183) ... 2 more Caused by: java.sql.SQLException: Log Record has been sent to the stream, but it cannot be applied to the store (Object null). This may cause recovery problems also. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 17 more Caused by: java.sql.SQLException: The store has been marked for shutdown by an earlier exception. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) ... 14 more Caused by: java.sql.SQLException: Page Page(0,Container(0, 1040)) could not be written to disk, please check if disk is full. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) ... 15 more Caused by: java.sql.SQLException: Java exception: 'The process cannot access the file because another process has locked a portion of the file: java.io.IOException'. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) ... 16 more Caused by: java.io.IOException: The process cannot access the file because another process has locked a portion of the file at sun.nio.ch.FileDispatcher.pwrite0(Native Method) at sun.nio.ch.FileDispatcher.pwrite(Unknown Source) at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.write(Unknown Source) at sun.nio.ch.FileChannelImpl.write(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer4.writeFull(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer4.writePage0(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer4.writePage(Unknown Source) at org.apache.derby.impl.store.raw.data.CachedPage.writePage(Unknown Source) at org.apache.derby.impl.store.raw.data.CachedPage.clean(Unknown Source) at org.apache.derby.impl.services.cache.ConcurrentCache.cleanAndUnkeepEntry(Unknown Source) at org.apache.derby.impl.services.cache.ConcurrentCache.cleanEntry(Unknown Source) at org.apache.derby.impl.services.cache.BackgroundCleaner.performWork(Unknown Source) at org.apache.derby.impl.services.daemon.BasicDaemon.serviceClient(Unknown Source) at org.apache.derby.impl.services.daemon.BasicDaemon.work(Unknown Source) at org.apache.derby.impl.services.daemon.BasicDaemon.run(Unknown Source) ... 1 more
I see that there is a message "could not be written to disk, please check if disk is full". Is there a chance that the disk is full?
No, that was the first thing I checked. There was at least 30 Gb available.
The derby error message:
The process cannot access the file because another process has locked a portion of the file
indicates that there are multiple processes accessing some of the database files. Only a single iTest process should be accessing these database files. Is it possible that someone was copying or deleting these files while iTest was running?
Not unless iTest itself was doing so. Well, it
is a PC, so maybe there's something mysterious going on in the background, but nothing we started.
Since only a single iTest process is allowed to work/attach to a workspace, it is hard or impossible to see how to iTest processes will be touch a single database. We will have to figure out what else is happening. May be the derby error is misleading and there is some underlying i/o error which results in this misleading message from derby.
We've only seen it once, and an itest restart made it go away. Makes it a bit hard to troubleshoot...
