[
https://issues.apache.org/jira/browse/JENA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088696#comment-13088696
]
Paolo Castagna edited comment on JENA-91 at 8/22/11 1:59 PM:
-------------------------------------------------------------
I've just your "patch" to TestTransSystem and a couple of additional pauses, it
now reliably outputs a "Different ids allocated: expected [000000000000004F],
got [0000000000000058]" error message (even when running just in memory,
setting MEM = true).
I do agree with you on "we need to dig to the bottom of this". It's time
dependent, random and probably a concurrency issue. Progress: we are now able
to replicate it. I have no hypothesis on the cause at the moment.
was (Author: castagna):
I've just your "patch" to TestTransSystem and a couple of additional
pauses, it now reliably outputs a "Different ids allocated: expected
[000000000000004F], got [0000000000000058]" error message.
I do agree with you on "we need to dig to the bottom of this". It's time
dependent, random and probably a concurrency issue. Progress: we are now able
to replicate it. I have no hypothesis on the cause at the moment.
> 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: TestTransSystem.patch, TestTransSystem2.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
