Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <user@jmeter.apache.org>
Received-SPF: softfail (nike.apache.org: transitioning domain of
 oliver_lloyd@hotmail.com does not designate 216.139.236.26 as permitted
 sender)
Date: Tue, 21 Feb 2012 06:08:24 -0800 (PST)
From: Oliver Lloyd <oliver_lloyd@hotmail.com>
To: jmeter-user@jakarta.apache.org
Message-ID: <1329833304127-5502286.post@n5.nabble.com>
In-Reply-To: <1329832657003-5502262.post@n5.nabble.com>
References: <1329818666371-5501731.post@n5.nabble.com>
 <1329819721350-5501779.post@n5.nabble.com>
 <1329832657003-5502262.post@n5.nabble.com>
Subject: Re: Liferay application testing - errors after 36 minutes
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This clearly looks like an application problem - if I had to take a punt I
would guess you have some sort of memory leak. Once you run out of memory
then the collector starts to thrash and you get the high CPU you see on the
app server. It's pretty simple to narrow this sort of stuff down - you just
have to think logically.

But none of this is anything to do with JMeter, you might get more millage
posting this problem elsewhere, maybe somewhere 
http://www.liferay.com/community/forums more specific to LifeRay .

That said, have you tried graphing the heap while the test is running - I
imagine that will help. A rather snappy Google search gave me 
http://www.liferay.com/web/shuyang.zhou/blog/-/blogs/liferay-jvm-tuning this 
which might help you.

-----
http://www.http503.com/
--
View this message in context: http://jmeter.512774.n5.nabble.com/Liferay-application-testing-errors-after-36-minutes-tp5501731p5502286.html
Sent from the JMeter - User mailing list archive at Nabble.com.

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