db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1560) When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory for large LOBs
Date Wed, 02 Jun 2010 12:53:38 GMT

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

Kristian Waagan closed DERBY-1560.
----------------------------------

    Fix Version/s: 10.3.3.1
       Resolution: Fixed

Closing.

> When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory
for large LOBs
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1560
>                 URL: https://issues.apache.org/jira/browse/DERBY-1560
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client
>    Affects Versions: 10.1.3.1
>            Reporter: Fernanda Pizzorno
>             Fix For: 10.3.3.1
>
>
> When a LOB is streamed from the Server to the Client, the Client reads all the data from
the stream into a byte array. This can cause OutOfMemoryError if the LOB is large > than
total memory in the VM.
> To avoid this problem, instead of reading the streamed data into a byte array, the Client
could read the data into a stream which will keep the data in memory when possible and store
the data on disk when there is not enough memory. This stream could be based on the implementation
suggested in DERBY-1341.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message