db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4294) java.lang.OutOfMemoryError from mailjdbc test after running for one hour from select * from REFRESH.INBOX
Date Wed, 01 Jul 2009 12:36:47 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726035#action_12726035
] 

Knut Anders Hatlen commented on DERBY-4294:
-------------------------------------------

That's interesting. So it would seem that the bulk fetching stores the rows in a DataValueDescriptor[fetchSize][numColumns]
object, which shouldn't take that much memory since the CLOBs are represented by unmaterialized
SQLClob objects. But when ij calls getString() on the result set, the SQLClob is materialized
and will stay materialized until all the rows in the group have been read.

This problem is somewhat related to DERBY-1511. Disabling bulk fetching for long columns should
address both issues, I think. Using getClob().getSubString() would probably address the problem
in this issue (but not the one in DERBY-1511).

> java.lang.OutOfMemoryError from mailjdbc test after running for one hour from select
* from REFRESH.INBOX
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4294
>                 URL: https://issues.apache.org/jira/browse/DERBY-4294
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.3.3.0
>         Environment: Window Vista
>            Reporter: Lily Wei
>         Attachments: Derby4294_pid6920.zip, Heapspaceerror.zip
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> After running mailjdbc test on 10.3 branch, select * from REFRESH.INBOX gave me error
like:
> ERROR XJ001: Java exception: 'Java heap space: java.lang.OutOfMemoryError'
> I also see the same error on 10.5 branch. 
> I inculde my mailsdb directory in this bug too.
> How to reproduce this issue:
> 1. cd mailjdbc
> 2. java org.apache.derbyTesting.system.mailjdbc.MailJdbc embedded
> 3. Wait for an hour and ignore Primary key violation error 
> ( : INFO :Refresh Thread : Error while inserting attachments:The statement was ab
> orted because it would have caused a duplicate key value in a unique or primary
> key constraint or unique index identified by 'ATTACH__PK' defined on 'ATTACH'.)

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