db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3524) NullPointerException in Xact.openContainer() when running suites.All on 10.3.
Date Tue, 11 Mar 2008 16:52:46 GMT
NullPointerException in Xact.openContainer() when running suites.All on 10.3.

                 Key: DERBY-3524
                 URL: https://issues.apache.org/jira/browse/DERBY-3524
             Project: Derby
          Issue Type: Bug
          Components: Regression Test Failure, Store
    Affects Versions:
            Reporter: A B
            Priority: Minor

When running suites.All on a 10.3 codeline at svn # 634534 with ibm15, I saw a total of *45*
failures, all caused by NullPointerExceptions that occurred as part of a call to Xact.openContainer().
 An example of one of the stack traces is:

 at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
 at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
 at org.apache.derby.impl.store.raw.xact.Xact.openContainer(Unknown Source)
 at org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.init(Unknown Source)
 at org.apache.derby.impl.store.access.heap.Heap.open(Unknown Source)
 at org.apache.derby.impl.store.access.heap.HeapPostCommit.performWork(Unknown Source)
 at org.apache.derby.impl.store.raw.xact.Xact.postTermination(Unknown Source)
 at org.apache.derby.impl.store.raw.xact.Xact.completeCommit(Unknown Source)
 at org.apache.derby.impl.store.raw.xact.Xact.commit(Unknown Source)
 at org.apache.derby.impl.store.raw.xact.Xact.commit(Unknown Source)
 at org.apache.derby.impl.store.access.RAMTransaction.commit(Unknown Source)

The 45 failures are spread across the following JUnit tests: upgradeTests.changes10_3, BlobStoredProcedureTest,
ClobStoredProcedureTest, and DatabaseMetaDataTest.  The call stack leading up to Xact.openContainer()
is not always the same for the different failures.

I ran each of the aforementioned JUnit tests on my local machine and they all ran without
error, so I am unable to reproduce the problem.  But filing Jira for tracking...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message