db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-1560) When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory for large LOBs
Date Wed, 06 Dec 2006 14:44:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1560?page=all ]

Rick Hillegas reassigned DERBY-1560:
------------------------------------

    Assignee:     (was: Fernanda Pizzorno)

Fernanda has moved on to other responsibilities and I do not expect that she will tackle this
issue.

> When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory
for large LOBs
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1560
>                 URL: http://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.2.3.0
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message