Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 47701 invoked from network); 25 May 2010 11:51:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 May 2010 11:51:50 -0000 Received: (qmail 80015 invoked by uid 500); 25 May 2010 11:51:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 79897 invoked by uid 500); 25 May 2010 11:51:48 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 79885 invoked by uid 99); 25 May 2010 11:51:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 May 2010 11:51:47 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 May 2010 11:51:45 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o4PBpN7q022352 for ; Tue, 25 May 2010 11:51:24 GMT Message-ID: <32679932.32031274788283850.JavaMail.jira@thor> Date: Tue, 25 May 2010 07:51:23 -0400 (EDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1560) When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory for large LOBs In-Reply-To: <30269684.1153491914002.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871105#action_12871105 ] Kristian Waagan commented on DERBY-1560: ---------------------------------------- I propose that we close this issue, because I believe the issue went away when locators were introduced. Note that some actions will result in the entire LOB being kept in memory, for instance executing Clob.getSubString(1, ) and Blob.getBytes(). This is a necessity, and is as designed. > 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 > > 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.