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'.)
|Workflow||jira [ 12467117 ]||Default workflow, editable Closed status [ 12802805 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||10.7.1.1 [ 12315564 ]|
|Affects Version/s||10.6.2.1 [ 12315343 ]|
|Affects Version/s||10.5.3.0 [ 12314117 ]|
|Affects Version/s||10.4.2.0 [ 12313345 ]|
|Issue & fix info||[Release Note Needed, Repro attached]||[Repro attached]|
|Bug behavior facts||[Crash]|
|Issue & fix info||[Release Note Needed]||[Release Note Needed, Repro attached]|
[ 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). ]
|Original Estimate||0h [ 0 ]|
|Remaining Estimate||0h [ 0 ]|
|Issue & fix info||[Existing Application Impact]||[Release Note Needed]|