db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Williamson (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3009) Out of memory error when creating a very large table
Date Wed, 15 Aug 2007 08:59:31 GMT
Out of memory error when creating a very large table

                 Key: DERBY-3009
                 URL: https://issues.apache.org/jira/browse/DERBY-3009
             Project: Derby
          Issue Type: Bug
    Affects Versions:
         Environment: Win XP Pro
            Reporter: Nick Williamson

When creating an extremely large table (c.50 indexes, c.50 FK constraints), IJ crashes with
an out of memory error. The table can be created successfully if it is done in stages, each
one in a different IJ session.

>From Kristian Waagan:

"With default settings on my machine, I also get the OOME.
A brief investigation revealed a few things:

  1) The OOME occurs during constraint additions (with ALTER TABLE ... 
ADD CONSTRAINT). I could observe this by monitoring the heap usage.

  2) The complete script can be run by increasing the heap size. I tried with 256 MB, but
the monitoring showed usage peaked at around 150 MB.

  3) The stack traces produced when the OOME occurs varies (as could be expected).

  4) It is the Derby engine that "produce" the OOME, not ij (i.e. when I ran with the network
server, the server failed).

I have not had time to examine the heap content, but I do believe there is a bug in Derby.
It seems some resource is not freed after use."

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message