db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: JVM memory settings for running suites.All
Date Wed, 06 Jul 2011 16:14:39 GMT
On 7/6/2011 8:35 AM, Knut Anders Hatlen wrote:
> I increased that setting to 48M in the nightlies a while back to silence
> the warning, but it has reappeared in many of them now, so I'll see if
> 64M works better. The warning appears to be harmless, though. The tests
> will continue, but possibly slower since the compiler is turned off.
> This has typically happened during the upgrade testing when I've seen
> it, probably because we have ~20 versions of every Derby class loaded at
> the same time.
I've often wondered about this also in the context of the permgen space. 
If derby is shutdown between testing versions, shouldn't we have just 
two loaded at any one time?

View raw message