You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by srikanth peddireddy <sr...@yahoo.co.in> on 2005/06/30 10:16:35 UTC

Errors in jmeter and tomcat at higher loads

Hi All,

Iam doing the  loadtest on one of our web application deployed on tomcat. Both Tomcat and Jmeter are running on a very high end machines (4-proc 3 GB RAM machine  and 2-proc 1.5 GB machines respectivelhy).

When Iam running a particular test whose structure would be like 

ThreadGrp

   |____RequestUserAuthentication (which takes ID and PWD as params)

   |____MainPage (which is shown to valid users)

   |____MainPageSub (Some page loaded into sub frame of main page)

   |____LoopController (forever set)

              |___Page1.jsp (bcoz of timer Page1 Called after 1 min of mainpage)

                        |___ConstantTimer(Delay set as 60000)

              |____InterLeaveController

                      |___OnlyOnce Controller

                            |___Page2.jsp

                      |___OnlyOnce Controller

                            |___Page3.jsp

                      |___OnlyOnce Controller

                            |___Page4.jsp

 
When I  ran this test with thread count = 1000 and rampup period =200 seconds, I started seeing errors in  Jmeter after some 865 requests are sent to mainpage and MainPageSub  (all 1000 requests are sent to RequestUserAuthentication) (these request counts are according to Aggregate Report Listener)

Following is the error  shown in Jmeter (Tree listener)

java.io.IOException: Stream closed
 at java.io.BufferedInputStream.ensureOpen(Unknown Source)
 at java.io.BufferedInputStream.read(Unknown Source)
 at java.io.FilterInputStream.read(Unknown Source)
 at org.apache.jmeter.protocol.http.sampler.HTTPSampler.readResponse(HTTPSampler.java:263)
 at org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.java:496)
 at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:590)
 at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:578)
 at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:281)
 at java.lang.Thread.run(Unknown Source)


But I let the test continue like that even Iam seeing errors, then after a while i saw a java.lang.OutOfMemoryError in tomcat
When I manually stopped the test and jmeter is still stopping the threads , tomcat started giving out following error messages


SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
t.util.net.LeaderFollowerWorkerThread@8f3eac, terminating thread
Jun 30, 2005 3:13:15 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnabl
e run
SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
t.util.net.LeaderFollowerWorkerThread@8f3eac, terminating thread
Jun 30, 2005 3:13:18 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnabl
e run
SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
t.util.net.LeaderFollowerWorkerThread@8f3eac, terminating thread
Jun 30, 2005 3:13:44 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnabl
e run

..................

I cant understand what should I conclude from this -- 
 whether jmeter is unable to create and maintain somuch load   or
 tomcat is unable to handle so many requests


Point to note here is test ran successfully with thread count=50 and ramp-up = 100 seconds

any help / input in this would be appreciated

 

regards

Srikanth.P

		
---------------------------------
 Free antispam, antivirus and 1GB to save all your messages
 Only in Yahoo! Mail: http://in.mail.yahoo.com

Re: Errors in jmeter and tomcat at higher loads

Posted by Praveen Kallakuri <pk...@gmail.com>.
Your test is too intense. Do you have any delay between consecutive
samplers in your test plan? You might very well be running a DOS
attack against your server.

As for the IO exceptions,.. I used to get IO exceptions in jmeter when
there were too many threads receiving a response from the server.

What I did was split up the number of jmeter instances generating
load.. instead of 1 jmeter client running 1000 threads, I used 2 or 3
jmeter instances on different machines.. I was able to reach the
concurrency desired, besides it being a more realistic test.

I still cannot explain why this works... most probably, I guessed that
there were simply too many channels open between jmeter and the
appserver.. something in the network route (a switch, or maybe the
bandwidth supporting by the ethernet itself) was becoming a
bottleneck. Either this or jmeter, given its resources simply cannot
keep so many channels open.

I suggest you monitor the capacities of various network components
while running your test in order to see whether there is some
bottleneck there... or simply like I did, split up the source of the
traffic and see whether you can generate the same load.

On 6/30/05, srikanth peddireddy <sr...@yahoo.co.in> wrote:
> 
> Hi All,
> 
> Iam doing the  loadtest on one of our web application deployed on tomcat. Both Tomcat and Jmeter are running on a very high end machines (4-proc 3 GB RAM machine  and 2-proc 1.5 GB machines respectivelhy).
> 
> When Iam running a particular test whose structure would be like
> 
> ThreadGrp
> 
>    |____RequestUserAuthentication (which takes ID and PWD as params)
> 
>    |____MainPage (which is shown to valid users)
> 
>    |____MainPageSub (Some page loaded into sub frame of main page)
> 
>    |____LoopController (forever set)
> 
>               |___Page1.jsp (bcoz of timer Page1 Called after 1 min of mainpage)
> 
>                         |___ConstantTimer(Delay set as 60000)
> 
>               |____InterLeaveController
> 
>                       |___OnlyOnce Controller
> 
>                             |___Page2.jsp
> 
>                       |___OnlyOnce Controller
> 
>                             |___Page3.jsp
> 
>                       |___OnlyOnce Controller
> 
>                             |___Page4.jsp
> 
> 
> When I  ran this test with thread count = 1000 and rampup period =200 seconds, I started seeing errors in  Jmeter after some 865 requests are sent to mainpage and MainPageSub  (all 1000 requests are sent to RequestUserAuthentication) (these request counts are according to Aggregate Report Listener)
> 
> Following is the error  shown in Jmeter (Tree listener)
> 
> java.io.IOException: Stream closed
>  at java.io.BufferedInputStream.ensureOpen(Unknown Source)
>  at java.io.BufferedInputStream.read(Unknown Source)
>  at java.io.FilterInputStream.read(Unknown Source)
>  at org.apache.jmeter.protocol.http.sampler.HTTPSampler.readResponse(HTTPSampler.java:263)
>  at org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.java:496)
>  at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:590)
>  at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:578)
>  at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:281)
>  at java.lang.Thread.run(Unknown Source)
> 
> 
> But I let the test continue like that even Iam seeing errors, then after a while i saw a java.lang.OutOfMemoryError in tomcat
> When I manually stopped the test and jmeter is still stopping the threads , tomcat started giving out following error messages
> 
> 
> SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
> t.util.net.LeaderFollowerWorkerThread@8f3eac, terminating thread
> Jun 30, 2005 3:13:15 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnabl
> e run
> SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
> t.util.net.LeaderFollowerWorkerThread@8f3eac, terminating thread
> Jun 30, 2005 3:13:18 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnabl
> e run
> SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
> t.util.net.LeaderFollowerWorkerThread@8f3eac, terminating thread
> Jun 30, 2005 3:13:44 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnabl
> e run
> 
> ..................
> 
> I cant understand what should I conclude from this --
>  whether jmeter is unable to create and maintain somuch load   or
>  tomcat is unable to handle so many requests
> 
> 
> Point to note here is test ran successfully with thread count=50 and ramp-up = 100 seconds
> 
> any help / input in this would be appreciated
> 
> 
> 
> regards
> 
> Srikanth.P
> 
> 
> ---------------------------------
>  Free antispam, antivirus and 1GB to save all your messages
>  Only in Yahoo! Mail: http://in.mail.yahoo.com
> 


-- 
                                     k.p.

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