[
https://issues.apache.org/jira/browse/JENA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083519#comment-13083519
]
Simon Helsen commented on JENA-91:
----------------------------------
I just finished the instrumentation of my own code with the TDB-TX transaction
API and now I can see that after I disconnect/re-connect, a write causes the
following messages in my log:
16:50:27,351 [1606049722@qtp-2056813208-23] INFO com.ibm.team.jfs
- CRJZS5347I Indexing: resumed
ModelWriteActivity:
16:50:27,826 [jazz.jfs.indexer.jfs_tests_default_consumer_name.triple] ERROR
com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in the read
cache
16:50:27,830 [jazz.jfs.indexer.jfs_tests_default_consumer_name.triple] ERROR
com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in the read
cache
16:50:27,834 [jazz.jfs.indexer.jfs_tests_default_consumer_name.triple] ERROR
com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in the read
cache
16:50:27,837 [jazz.jfs.indexer.jfs_tests_default_consumer_name.triple] ERROR
com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in the read
cache
16:50:27,841 [jazz.jfs.indexer.jfs_tests_default_consumer_name.triple] ERROR
com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in the read
cache
16:50:27,844 [jazz.jfs.indexer.jfs_tests_default_consumer_name.triple] ERROR
com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in the read
cache
-> finish execution: 35ms
I presume again that this is a consequence of a corrupted disk index.
> 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
> Environment: Windows (and I presume any little endian system)
> Reporter: Simon Helsen
> Assignee: Andy Seaborne
> Priority: Critical
>
> 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
