[
https://issues.apache.org/jira/browse/JENA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114814#comment-13114814
]
Simon Helsen commented on JENA-91:
----------------------------------
ok, so just running TestTransSystemJena91 like you asked (after updating
everything, including ARQ), produced the following output
TestTransSystemJena91
Mon Sep 26 13:15:09 EDT 2011
java.version = 1.6.0
java.vendor = IBM Corporation
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = jvmwa6460sr9-20110624_85526
java.vm.version = 2.4
java.vm.vendor = IBM Corporation
java.vm.name = IBM J9 VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.info = JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64
jvmwa6460sr9-20110624_85526 (JIT enabled, AOT enabled)
J9VM - 20110624_085526
JIT - r9_20101028_17488ifx17
GC - 20101027_AA
java.class.version = 50.0
java.specification.version = 1.6
java.specification.vendor = Sun Microsystems Inc.
os.name = Windows 7
os.version = 6.1 build 7601 Service Pack 1
java.class.path =
D:\jfsDev\TxTDB\classes;C:\Users\shelsen\.m2\repository\com\hp\hpl\jena\arq\2.8.9-SNAPSHOT\arq-2.8.9-SNAPSHOT.jar;C:\Users\shelsen\.m2\repository\com\hp\hpl\jena\arq\2.8.9-SNAPSHOT\arq-2.8.9-SNAPSHOT-tests.jar;C:\Users\shelsen\.m2\repository\com\ibm\icu\icu4j\3.4.4\icu4j-3.4.4.jar;C:\Users\shelsen\.m2\repository\com\hp\hpl\jena\iri\0.8\iri-0.8.jar;C:\Users\shelsen\.m2\repository\com\hp\hpl\jena\jena\2.6.4\jena-2.6.4.jar;C:\Users\shelsen\.m2\repository\com\hp\hpl\jena\jena\2.6.4\jena-2.6.4-tests.jar;C:\Users\shelsen\.m2\repository\junit\junit\4.8.2\junit-4.8.2.jar;C:\Users\shelsen\.m2\repository\log4j\log4j\1.2.16\log4j-1.2.16.jar;C:\Users\shelsen\.m2\repository\org\apache\lucene\lucene-core\2.3.1\lucene-core-2.3.1.jar;C:\Users\shelsen\.m2\repository\org\slf4j\slf4j-api\1.6.1\slf4j-api-1.6.1.jar;C:\Users\shelsen\.m2\repository\org\slf4j\slf4j-log4j12\1.6.1\slf4j-log4j12-1.6.1.jar;C:\Users\shelsen\.m2\repository\stax\stax-api\1.0.1\stax-api-1.0.1.jar;C:\Users\shelsen\.m2\repository\org\codehaus\woodstox\wstx-asl\3.2.9\wstx-asl-3.2.9.jar;C:\Users\shelsen\.m2\repository\xerces\xercesImpl\2.7.1\xercesImpl-2.7.1.jar
java.home = C:\development\jdk\ibm60\jre
START (disk[direct], 1000 iterations)
000:
....................................................................................................
100:
................................................com.hp.hpl.jena.tdb.TDBException:
Different ids for
"-2493539583195906921"^^http://www.w3.org/2001/XMLSchema#long: allocated:
expected [00000000000001EA], got [00000000000001A7]
at
com.hp.hpl.jena.tdb.transaction.NodeTableTrans.append(NodeTableTrans.java:178)
at
com.hp.hpl.jena.tdb.transaction.NodeTableTrans.writeNodeJournal(NodeTableTrans.java:210)
at
com.hp.hpl.jena.tdb.transaction.NodeTableTrans.commitPrepare(NodeTableTrans.java:190)
at
com.hp.hpl.jena.tdb.transaction.Transaction.prepare(Transaction.java:93)
at
com.hp.hpl.jena.tdb.transaction.Transaction.commit(Transaction.java:77)
at com.hp.hpl.jena.tdb.DatasetGraphTxn.commit(DatasetGraphTxn.java:26)
at tx.TestTransSystemJena91$Writer.call(TestTransSystemJena91.java:291)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
> extremely large buffer is being created in ObjectFileStorage
> ------------------------------------------------------------
>
> Key: JENA-91
> URL: https://issues.apache.org/jira/browse/JENA-91
> Project: Jena
> Issue Type: Bug
> Components: TDB
> Reporter: Simon Helsen
> Assignee: Andy Seaborne
> Priority: Critical
> Attachments: JENA-91_NodeTableTrans_r1159121.patch,
> TestTransSystem.patch, TestTransSystem2.patch, TestTransSystem3.patch,
> TestTransSystem4.patch
>
>
> I tried to debug the OME and check why a bytebuffer is causing my native
> memory to explode in almost no time. It all seems to happen in this bit of
> code in com.hp.hpl.jena.tdb.base.objectfile.ObjectFileStorage (lines 243
> onwards)
> // No - it's in the underlying file storage.
> lengthBuffer.clear() ;
> int x = file.read(lengthBuffer, loc) ;
> if ( x != 4 )
> throw new
> FileException("ObjectFile.read("+loc+")["+filesize+"]["+file.size()+"]:
> Failed to read the length : got "+x+" bytes") ;
> int len = lengthBuffer.getInt(0) ;
> ByteBuffer bb = ByteBuffer.allocate(len) ;
> My debugger shows that x==4. It also shows the lengthBuffer has the following
> content: [111, 110, 61, 95]. This amounts to the value of len=1869495647,
> which is rather a lot :-) Obviously, the next statement (ByteBuffer.allocate)
> causes the OME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
