[
https://issues.apache.org/jira/browse/JENA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087639#comment-13087639
]
Paolo Castagna commented on JENA-91:
------------------------------------
Simon, I tried to run TestTransSystem.java with your changes. The warnings in
this case are misleading, a false alarm, since your code adds triples to named
graphs while the test checks for the effects on the default graph. I do not see
any error or exceptions.
I also tried to write separate sequential tests using the Jena APIs (as you do)
mixed with with direct calls to DatasetGraph's methods. Once again, I see no
errors or exceptions.
The error "ERROR com.hp.hpl.jena.tdb.base.block.BlockMgrCache - write: Block in
the read cache", which you reported above, originates in BlockMgrCache which is
used only if FileMode.direct is used.
There is a flag in TestTransSystem to run in "direct" or "mapped" mode. Once
again, I've been running TestTransSystem in "direct" or "mapped" mode and I see
no errors or exceptions.
If you manage to see an error running TestTransSystem.java or any modified
version of it, please, attach a copy of the file to this issue.
> 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
> Attachments: TestTransSystem.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
