[jira] [Resolved] (DAFFODIL-2194) buffered data output stream has a chunk limit of 2GB

["Josh Adams (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Adams resolved DAFFODIL-2194.
----------------------------------
      Assignee: Dave Thompson  (was: Josh Adams)
    Resolution: Fixed

This should be completely fixed now, as of commit fb533b6c28904b63ce1cd61d4676a64912f0c7e2

 

Commit fb533b6c28904b63ce1cd61d4676a64912f0c7e2 fixes the 2GB limit when unparsing into a ByteArrayOutputStream by switching to a FileOutputStream once a specified limit has been reached.

 

Commit 1868257f306572512b6d000150508b60dec3ff0a fixes the heap sized limit issue when parsing.

> buffered data output stream has a chunk limit of 2GB
> ----------------------------------------------------
>
>                 Key: DAFFODIL-2194
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2194
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>            Reporter: Steve Lawrence
>            Assignee: Dave Thompson
>            Priority: Major
>             Fix For: 2.5.0
>
>
> A buffered data outupt stream is backed by a growable ByteArrayOutputStream, which can only grow to 2GB in size. So if we ever try to write more than 2GB to a buffered output stream during unparse (very possible with large blobs), we'll get an OutOfMemoryError.
> One potential solution is to be aware of the size of a ByteArrayOutputStream when buffering output and automatically create a split when it gets to 2GB in sizes. This will still require a ton of memory since we're buffering these in memoary, but we'll at least be able to unparse more than 2GB of continuous data. 
> Note that we should still be able to unparse more than 2GB of data total, as long as there so single buffer that's more than 2GB.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)