db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: out of memory error in replication tests
Date Fri, 26 Sep 2008 13:25:31 GMT
By the way: thanks to Ole, Mamta, and Bryan for responding to my 
original post. The MaxPermSize setting below fixed my problem.

Thanks,
-Rick

Ole Solberg wrote:
> In the regression tests reported at 
> http://dbtg.thresher.com/derby/test/ the following setting is used: 
> -XX:MaxPermSize=128M -Xmx256M
> The replication tests are run as part of suites.All.
>
>
>
> Mamta Satoor wrote:
>> Rick, I thought I would share that I have always run my junit tests
>> with -Xmx1024m. Not sure if I need that much but have not run out of
>> memory with that.
>>
>> Mamta
>>
>> On 9/16/08, Rick Hillegas <Richard.Hillegas@sun.com> wrote:
>>> Bryan Pendleton wrote:
>>>>> How much memory should we be giving the tests now
>>>>>
>>>> I ran "derbyall" and "junitreport" over the weekend
>>>> and didn't have to provide any special memory parameters.
>>>>
>>>> I don't know if I ran the replication tests, though; do
>>>> I have to do something special to run these?
>>>>
>>>> thanks,
>>>>
>>>> bryan
>>>>
>>>>
>>>>
>>> Thanks, Bryan. I didn't do anything special. One difference may be 
>>> that I
>>> have put the 10.4.1.3 and 10.4.2.0 releases in my upgrade test path 
>>> so I'm
>>> now running the upgrade tests against two additional starting points.
>>>
>>> Thanks,
>>> -Rick
>>>
>


Mime
View raw message