[ 
https://issues.apache.org/jira/browse/JENA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438045#comment-13438045
 ] 

Simon Helsen commented on JENA-299:
-----------------------------------

The issue I reported in this defect is gone. However, I am still observing 
another problem. Whenever I start the product all appears fine, but when I shut 
it down and then start again, I run into the following exception (i.e. some 
sort of corruption). I'll try to produce an independent test case. Perhaps 
there is a relation to JENA-301 as well?

13:44:31,484 [1311264296@qtp-145033381-5] ERROR com.ibm.team.jfs                
                    - @ID@E An unexpected problem occurred while processing a 
transactional model read activity
java.lang.UnsupportedOperationException: Quad: predicate cannot be null
        at com.hp.hpl.jena.sparql.core.Quad.<init>(Quad.java:61)
        at com.hp.hpl.jena.tdb.lib.TupleLib.quad(TupleLib.java:162)
        at com.hp.hpl.jena.tdb.lib.TupleLib.quad(TupleLib.java:153)
        at com.hp.hpl.jena.tdb.lib.TupleLib.access$100(TupleLib.java:45)
        at com.hp.hpl.jena.tdb.lib.TupleLib$4.convert(TupleLib.java:87)
        at com.hp.hpl.jena.tdb.lib.TupleLib$4.convert(TupleLib.java:83)
        at org.openjena.atlas.iterator.Iter$4.next(Iter.java:301)
        at 
com.hp.hpl.jena.tdb.store.GraphTDBBase$ProjectQuadsToTriples.next(GraphTDBBase.java:178)
        at 
com.hp.hpl.jena.tdb.store.GraphTDBBase$ProjectQuadsToTriples.next(GraphTDBBase.java:166)
        at 
com.hp.hpl.jena.util.iterator.WrappedIterator.next(WrappedIterator.java:80)
        at com.hp.hpl.jena.util.iterator.Map1Iterator.next(Map1Iterator.java:47)
        at 
com.hp.hpl.jena.util.iterator.WrappedIterator.next(WrappedIterator.java:80)
        at 
com.hp.hpl.jena.rdf.model.impl.StmtIteratorImpl.next(StmtIteratorImpl.java:45)
        at 
com.hp.hpl.jena.rdf.model.impl.StmtIteratorImpl.next(StmtIteratorImpl.java:33)
        at 
com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider$7.run(JenaTxTdbProvider.java:950)
        at 
com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider$7.run(JenaTxTdbProvider.java:1)
        at 
com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider.storeOperation(JenaTxTdbProvider.java:208)
        at 
com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider.readAndSetCurrentIndexSize(JenaTxTdbProvider.java:941)
        at 
com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider.connect(JenaTxTdbProvider.java:488)
        at 
com.ibm.team.jfs.rdf.internal.jena.JenaRdfService.connect(JenaRdfService.java:284)
                
> LeaveCriticalSection Error
> --------------------------
>
>                 Key: JENA-299
>                 URL: https://issues.apache.org/jira/browse/JENA-299
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: TDB
>    Affects Versions: TDB 0.9.4
>         Environment: windows 64 bit
>            Reporter: Simon Helsen
>            Assignee: Andy Seaborne
>            Priority: Critical
>             Fix For: TDB 0.9.4
>
>         Attachments: LeaveCriticalSectionTestCase.zip
>
>
> I have attached a standalone test case, which, when run with the latest 
> snapshot produces the following exception:
> Exception in thread "main" com.hp.hpl.jena.shared.JenaException: 
> leaveCriticalSection: No lock held (main) Thread R/W: 0/0 :: Model R/W: 0/0 
> (thread: main)
>       at 
> com.hp.hpl.jena.shared.LockMRSW.leaveCriticalSection(LockMRSW.java:175)
>       at 
> com.hp.hpl.jena.tdb.transaction.TransactionManager$TSM_WriteBackEndTxn.readerFinishes(TransactionManager.java:210)
>       at 
> com.hp.hpl.jena.tdb.transaction.TransactionManager.readerFinishes(TransactionManager.java:723)
>       at 
> com.hp.hpl.jena.tdb.transaction.TransactionManager.noteTxnAbort(TransactionManager.java:587)
>       at 
> com.hp.hpl.jena.tdb.transaction.TransactionManager.notifyAbort(TransactionManager.java:445)
>       at 
> com.hp.hpl.jena.tdb.transaction.Transaction.abort(Transaction.java:162)
>       at 
> com.hp.hpl.jena.tdb.transaction.DatasetGraphTxn.abort(DatasetGraphTxn.java:45)
>       at 
> com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction._abort(DatasetGraphTransaction.java:156)
>       at 
> com.hp.hpl.jena.tdb.migrate.DatasetGraphTrackActive.abort(DatasetGraphTrackActive.java:68)
>       at com.hp.hpl.jena.sparql.core.DatasetImpl.abort(DatasetImpl.java:149)
>       at 
> com.ibm.jena.test.LeaveCriticalSectionErrorTest.storeOperation(LeaveCriticalSectionErrorTest.java:57)
>       at 
> com.ibm.jena.test.LeaveCriticalSectionErrorTest.query1(LeaveCriticalSectionErrorTest.java:105)
>       at 
> com.ibm.jena.test.LeaveCriticalSectionErrorTest.main(LeaveCriticalSectionErrorTest.java:156)
> The sequence in the test case is to run 2 queries, 1 write and then again 2 
> queries:
>       test.query1();
>               test.query1();
>               test.write1();
>               test.query1();
>               test.query1();
> Somehow, the following sequence did not produce the exception:
>       test.query1();
>               test.query1();
>               test.write1();
>               test.query1();
> Note that the test case does not check the correctness of any results.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to