db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2027) JUnit suite All crashes with OutOfMemoryError when running LobLengthTest
Date Wed, 01 Nov 2006 16:24:17 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2027?page=all ]

Kristian Waagan updated DERBY-2027:

    Attachment: derby-2027-1a.diff

'derby-2027-1a.diff' fixes the OutOfMemoryError seen when running the All suite by using another
mechanism to provide the ~16 MB of data required in the test.
This patch is not a general solution to the OutOfMemoryError, since it might show up again
when adding more tests.

Ran the All suite without errors with Sun Java 1.5.0_07 (Client VM).
When running with Java SE 6 (b103), I got some errors in BlobClob4Blob a few times, but when
I run it now, everything works (3261 tests, ~550 sec). No idea why. Would be nice if someone
took the time to run All with Java SE 6 to confirm/deny my experience.

Please review/commit.

> JUnit suite All crashes with OutOfMemoryError when running LobLengthTest
> ------------------------------------------------------------------------
>                 Key: DERBY-2027
>                 URL: http://issues.apache.org/jira/browse/DERBY-2027
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>         Environment: General, but default heap space size for the VM used matters.
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>         Attachments: derby-2027-1a.diff
> The All suite crashes when running jdbcapi/LobLengthTest.
> It is reasonable to believe the memory usage accumulates and that this test makes the
memory usage too high.
> Looking at the test, it uses a ~16 MB byte array.
> This problem was reported on derby-dev: http://www.nabble.com/Out-of-memory-error-when-running-JUnit-suite-t2549103.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message