You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Manjula Kutty (JIRA)" <de...@db.apache.org> on 2005/10/29 02:08:59 UTC
[jira] Created: (DERBY-661) Java.lang.OutOfMemory error while inserting CLOBS
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
[jira] Commented: (DERBY-661) Java.lang.OutOfMemory error while inserting CLOBS
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-661?page=comments#action_12356547 ]
Manjula Kutty commented on DERBY-661:
-------------------------------------
The bug is not a regression bug.
I ran the same test with the same files of size 1M-3M and found the issue with 10.1 also.
> 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
[jira] Resolved: (DERBY-661) Java.lang.OutOfMemory error while inserting CLOBS
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ 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