Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 58012 invoked from network); 17 Sep 2008 04:53:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Sep 2008 04:53:12 -0000 Received: (qmail 51055 invoked by uid 500); 17 Sep 2008 04:53:09 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 51009 invoked by uid 500); 17 Sep 2008 04:53:09 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 50996 invoked by uid 99); 17 Sep 2008 04:53:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 21:53:09 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of msatoor@gmail.com designates 64.233.166.181 as permitted sender) Received: from [64.233.166.181] (HELO py-out-1112.google.com) (64.233.166.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2008 04:52:11 +0000 Received: by py-out-1112.google.com with SMTP id u52so2469266pyb.13 for ; Tue, 16 Sep 2008 21:52:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+Nsv05L5lV2F8jk0wUMgNlI0dWdlC2dmwn29MauP8ys=; b=IpgVh18+a+mcDUpQBffLrE98XT9P40E8HvvG8rTK74o4ALJ+51bNI8am8fsX5cAQFw e2+at9BJw19PQZs0qMmnN36vqMs/hsJNpRjPv47oB+CaaCUf2JSWaop8BH1CCS6mMEaj mVl5WuzbZ+fXUDpXsO8uqpiaUqq3/CCcAcXRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MTlt0/apEnskAdUZDC1ihUCLDxmQfRc3JUaJwmwq8Y1Z0pzTVVTKe499EYLzcvwYKz acAD5UgpBLa8EoOJoR/mWY1XRO8R8B5rCf0rnoOCSJuWySd0XPgNLmmUSN3hMtG7KnaL gZmFl7X3hRT0dhcl/ZlmnvnvbpeQuMCg7BK2g= Received: by 10.142.231.7 with SMTP id d7mr266862wfh.264.1221627146612; Tue, 16 Sep 2008 21:52:26 -0700 (PDT) Received: by 10.142.187.10 with HTTP; Tue, 16 Sep 2008 21:52:26 -0700 (PDT) Message-ID: Date: Tue, 16 Sep 2008 21:52:26 -0700 From: "Mamta Satoor" To: derby-dev@db.apache.org Subject: Re: out of memory error in replication tests In-Reply-To: <48D08B9C.4040609@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48CFC5D6.5080108@sun.com> <48CFD186.6000905@amberpoint.com> <48D08B9C.4040609@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org 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 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 >