[
https://issues.apache.org/jira/browse/DERBY-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040162#comment-13040162
]
Kristian Waagan commented on DERBY-4294:
----------------------------------------
I verified that the OOME doesn't occur with Derby 10.7 when running with a heap
of 64 MB (on Solaris). It did happen when I tried with Derby 10.6.
It would be good to get this issue resolved, which can be done in several ways:
a) Mark issue as fixed in 10.7 and be done with it.
b) Back-port DERBY-1511 as far back as is reasonable (10.5?).
c) Implement ij improvement (use getClob().getSubString()).
Opinions?
Option c will only affect the ij tool, not the Derby core (i.e. applications
written on top of Derby using JDBC won't benefit from it).
I'm fine with doing either a or b, but I think that in addition we should at
least log a JIRA for the 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
> Environment: Window Vista
> Reporter: Lily Wei
> Labels: derby_triage10_5_2
> 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
