Details

      Description

      The following error was observed for each of the three database run modes tested in CI. This error appeared in the first CI build after the commit of the change set logic to the 1.0.x maintenance branch.

      junit.framework.AssertionFailedError: Test failed: firstCause=java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException
      	at com.bigdata.rdf.sail.TestMROWTransactions.test_multiple_csem_transaction(TestMROWTransactions.java:385)
      Caused by: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException
      	at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator.checkFuture(BlockingBuffer.java:1481)
      	at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator._hasNext(BlockingBuffer.java:1658)
      	at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator.hasNext(BlockingBuffer.java:1521)
      	at com.bigdata.striterator.AbstractChunkedResolverator._hasNext(AbstractChunkedResolverator.java:327)
      	at com.bigdata.striterator.AbstractChunkedResolverator.hasNext(AbstractChunkedResolverator.java:303)
      	at com.bigdata.rdf.sail.TestMROWTransactions$1Reader.call(TestMROWTransactions.java:316)
      	at com.bigdata.rdf.sail.TestMROWTransactions$1Reader.call(TestMROWTransactions.java:295)
      	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      	at java.lang.Thread.run(Thread.java:680)
      Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException
      	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
      	at java.util.concurrent.FutureTask.get(FutureTask.java:83)
      	at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator.checkFuture(BlockingBuffer.java:1434)
      Caused by: java.lang.IllegalStateException
      	at com.bigdata.rdf.lexicon.LexiconRelation.getId2TermIndex(LexiconRelation.java:805)
      	at com.bigdata.rdf.lexicon.LexiconRelation.getTerms(LexiconRelation.java:1901)
      	at com.bigdata.rdf.store.BigdataStatementIteratorImpl.resolveChunk(BigdataStatementIteratorImpl.java:166)
      	at com.bigdata.rdf.store.BigdataStatementIteratorImpl.resolveChunk(BigdataStatementIteratorImpl.java:33)
      	at com.bigdata.striterator.AbstractChunkedResolverator$ChunkConsumerTask.call(AbstractChunkedResolverator.java:232)
      	at com.bigdata.striterator.AbstractChunkedResolverator$ChunkConsumerTask.call(AbstractChunkedResolverator.java:191)
      

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        I have verified that this issue is NOT present in the TERMS_REFACTOR_BRANCH.

        Show
        bryanthompson bryanthompson added a comment - I have verified that this issue is NOT present in the TERMS_REFACTOR_BRANCH.
        Hide
        bryanthompson bryanthompson added a comment -

        Actually, this is showing up consistently in CI for the TERMS_REFACTOR_BRANCH as well.

        Show
        bryanthompson bryanthompson added a comment - Actually, this is showing up consistently in CI for the TERMS_REFACTOR_BRANCH as well.
        Hide
        martyncutcher martyncutcher added a comment -

        checkDeferredFrees in RWStore must ensure that there is no session protection when clearing commit records. Previously this was checked prior to any call from within the RWStore. No the call is made from AbstractJournal so the additional check is required.

        This appears to fix the problem for the RWStore but I will check the other Journal modes before marking as fixed

        Show
        martyncutcher martyncutcher added a comment - checkDeferredFrees in RWStore must ensure that there is no session protection when clearing commit records. Previously this was checked prior to any call from within the RWStore. No the call is made from AbstractJournal so the additional check is required. This appears to fix the problem for the RWStore but I will check the other Journal modes before marking as fixed
        Hide
        bryanthompson bryanthompson added a comment -

        Committed revision: r5812.

        Show
        bryanthompson bryanthompson added a comment - Committed revision: r5812.

          People

          • Assignee:
            martyncutcher martyncutcher
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: