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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/06/01 12:53:47 UTC

[jira] [Updated] (DERBY-4294) java.lang.OutOfMemoryError from mailjdbc test after running for one hour from select * from REFRESH.INBOX

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

Kristian Waagan updated DERBY-4294:
-----------------------------------

     Issue & fix info: [Repro attached]  (was: [Release Note Needed, Repro attached])
    Affects Version/s: 10.4.2.0
                       10.5.3.0
                       10.6.2.1
        Fix Version/s: 10.7.1.1

Created DERBY-5257 to track the proposed ij improvement.

> 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, 10.4.2.0, 10.5.3.0, 10.6.2.1
>         Environment: Window Vista
>            Reporter: Lily Wei
>              Labels: derby_triage10_5_2
>             Fix For: 10.7.1.1
>
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira