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] Updated: (DERBY-4294) java.lang.OutOfMemoryError from mailjdbc test after running for one hour from select * from REFRESH.INBOX
Date Tue, 30 Jun 2009 21:38:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-4294:
--------------------------------------


I think you got the the digits right, but the total size of the CLOBs is 24MB, so they may
exhaust a small heap if they for some reason aren't freed when moving to the next row.

For the record, I didn't see the OOME when I tested with default heap settings on JDK 1.6.0_13
on OpenSolaris, but I did see it when reduced the heap size to 64 MB (-Xmx64M).

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