Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <957893109.1130889716003.JavaMail.jira@ajax.apache.org>
Date: Wed, 2 Nov 2005 01:01:56 +0100 (CET)
From: "Mike Matrigali (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-661) Java.lang.OutOfMemory error while
 inserting CLOBS
In-Reply-To: <2134126084.1130544539008.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-661?page=all ]
     
Mike Matrigali resolved DERBY-661:
----------------------------------

    Resolution: Duplicate

This bug is the same as DERBY-352

> Java.lang.OutOfMemory error while inserting CLOBS
> -------------------------------------------------
>
>          Key: DERBY-661
>          URL: http://issues.apache.org/jira/browse/DERBY-661
>      Project: Derby
>         Type: Bug
>   Components: Store
>     Versions: 10.1.1.0, 10.1.1.1
>     Reporter: Manjula Kutty

>
> When I ran my test with v10.1.2 ,of inserting rows with CLOBs sizes ranging between 1M-3M for about 15 minutes, the OutOfMemeory Exception was thrown. 
> While running same test with v10.1.0,  I didn't see this issue. It may be due to the a wide range of CLOBs size from 1K- 3M I used that time.
> The same test with 1M-3M of CLOBS runs fine with the v10.2(main). DERBY-352-not materializing streams, must have solved this issue.
> Please port Sunitha's patch (svn: 306822) to 10.1.2

-- 
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