You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/03/21 17:49:40 UTC
[jira] [Issue Comment Edited] (JENA-224) TDBException: Different
ids for ...: allocated: expected [...], got [...]
[ https://issues.apache.org/jira/browse/JENA-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234476#comment-13234476 ]
Andy Seaborne edited comment on JENA-224 at 3/21/12 4:49 PM:
-------------------------------------------------------------
The first run crashes the transaction system (because of the corrupt UTF-8) -- of course, the second run may fail. It's effect, not cause. I don't see any relation to JENA-163 except for the fact the system is broken.
was (Author: andy.seaborne):
The first run crashes the transaction system (because of the corrupt UTF-8) -- of course, the second run may fail. It's effect, not cause.
> TDBException: Different ids for ...: allocated: expected [...], got [...]
> -------------------------------------------------------------------------
>
> Key: JENA-224
> URL: https://issues.apache.org/jira/browse/JENA-224
> Project: Apache Jena
> Issue Type: Bug
> Components: TDB
> Affects Versions: TDB 0.9.0
> Reporter: Paolo Castagna
> Attachments: TestTDBCorruption.java
>
>
> In the attached test I have a WRITE transaction which fails (and I do not close the dataset).
> I run the test twice (the second time, the TDB database already exists) and I see:
> {code}
> 15:21:57 WARN NodeTableTrans :: Txn[1]/W journalStartOffset not zero: 109/0x6D
> ************* UNEXPECTED [1]
> Different ids for file:///opt/workspaces/jena/jena-examples/s: allocated: expected [000000000000006D], got [0000000000000000]
> >>>>>>>>>>
> label = nodes
> txn = Transaction: 1 : Mode=WRITE : State=PREPARING : /opt/workspaces/jena/jena-examples/target/tdb_corruption/
> offset = 109
> journalStartOffset = 109
> journal = nodes.dat-jrnl
> com.hp.hpl.jena.tdb.TDBException: Different ids for file:///opt/workspaces/jena/jena-examples/s: allocated: expected [000000000000006D], got [0000000000000000]
> at com.hp.hpl.jena.tdb.transaction.NodeTableTrans.inconsistent(NodeTableTrans.java:212)
> at com.hp.hpl.jena.tdb.transaction.NodeTableTrans.append(NodeTableTrans.java:200)
> at com.hp.hpl.jena.tdb.transaction.NodeTableTrans.writeNodeJournal(NodeTableTrans.java:306)
> at com.hp.hpl.jena.tdb.transaction.NodeTableTrans.commitPrepare(NodeTableTrans.java:266)
> at com.hp.hpl.jena.tdb.transaction.Transaction.prepare(Transaction.java:131)
> at com.hp.hpl.jena.tdb.transaction.Transaction.commit(Transaction.java:112)
> at com.hp.hpl.jena.tdb.transaction.DatasetGraphTxn.commit(DatasetGraphTxn.java:40)
> at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction._commit(DatasetGraphTransaction.java:106)
> at com.hp.hpl.jena.tdb.migrate.DatasetGraphTrackActive.commit(DatasetGraphTrackActive.java:60)
> at com.hp.hpl.jena.sparql.core.DatasetImpl.commit(DatasetImpl.java:143)
> at dev.TestTDBCorruption.test(TestTDBCorruption.java:54)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:69)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:48)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:292)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {code}
> See also:
> - http://markmail.org/thread/bt4ok2iqr4urar2d
--
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