Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4E04438C.7040207@mpexnet.de>
Date: Fri, 24 Jun 2011 09:58:04 +0200
From: Felix Frank <ff@mpexnet.de>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.17) Gecko/20110606 Icedove/3.1.10
MIME-Version: 1.0
To: JMeter Users List <jmeter-user@jakarta.apache.org>
Subject: Re: jmeter.threads.JMeterThread: Test failed!
 java.lang.OutOfMemoryError:
 GC overhead limit exceeded
References: <1308860779035-4518941.post@n5.nabble.com>
In-Reply-To: <1308860779035-4518941.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 06/23/2011 10:26 PM, jsheth wrote:
> 200 threads with ramp up period set to 1000. Tried changing to different
> ramp up periods to same result.

I would be amazed if this had helped, honestly.

> I do have summary and aggregate report listeners

If the problem occurs after the test has been running for a while,
disabling the Aggregate Report will help (why do you want it, anyway?)

> any ideas?

http://jakarta.apache.org/jmeter/usermanual/best-practices.html#lean_mean

If your Test Plan is too elaborate, Threads become very expensive.

If feasible, allow for a larger heap.

HTH,
Felix

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org