Chris wrote:
> Hi,
>
> i think i've found a bug in derby. i'm following the guidelines from
> the website and posting it here before reporting it just to make sure it
> *is* a bug!
>
> I'm running a set of ~50000 queries on one table, using inserts and
> updates, and i want to be able to roll them back so i turned off
> autocommit using setAutoCommit(false). As the update runs, the memory
> used by the JVM increases continually until i get the following
> exception about 20% of the way through:
>
> ERROR 40XT0: An internal error was identified by RawStore module.
> at
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java)
It looks like a bug, but a reproducible case would be needed to start
trying to fix it. Is there a chance you could post code that shows this
behaviour?
There may also be an earlier error the is the real problem, try checking
in your derby.log file.
Thanks,
Dan.
|