db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: OOM errors with suites.All
Date Mon, 19 Mar 2007 23:03:03 GMT
Myrna van Lunteren wrote:
> Hi,
> I'm having the most amazingly hard time running suites.All.
> I've gone to a clean(no modifications by me) trunk, updated to
> revision 520050, with sane jars, on the fastest machine available to
> me at this time, and I still see errors.
> I can vary the point of the OutOfMemory error by using a different
> test runner - for instance, junit.textui.TestRunner vs.
> junit.swingui.TestRunner, or using the ant junit-all target (that on
> my slower machine), but I don't think any of it is good.
> I seem to consistently see an OOM in the test jdbcapi/LobLengthTest.
> I found some old references to this, dating from August, but I don't
> see a solution.

The discussion has been happening in DERBY-2344


I think DERBY-2380 is part of the problem, until that is fixed it might 
be worth add some Derby shutdowns to free up the memory.


View raw message