To debug my issue, I had to strip the JMeter test down to the bare minimum that 
would still reproduce the issue. Then I tried to
separate out parts that might affect the issue. In my case, going straight to 
the Tomcat java app server (bypassing the Apache web
server 'proxy') eliminated the problem. This allowed me to focus on the Apache 
config - and that's when my system admin noticed that
someone had enabled the iptables and ip6tables on the Apache server.

For your problem, the debugging will be much the same - try to isolate the 
JMeter and server portions of the test to the bare
minimum, then eliminate parts that might affect the test until you identify the 
part that is causing the delay.

Also, just out of curiosity, what sort of network connection are you using for 
your test? We had an isolated 1000Mbps switch with a
12Gbps backplane running our tests (so only the test boxes and JMeter were on 
the network). Keeping your test traffic isolated from
other network activity is crucial to a reliable (and repeatable) test 
environment. If you have a 1Gbps switch, that's probably good
- but even so, if you have strange delays on the communications - make sure you 
look at the switch to see if is throwing errors or
running out of bandwidth on the switch backplane.

--
Robin D. Wilson
Sr. Director of Web Development
KingsIsle Entertainment, Inc.
VOICE: 512-777-1861
www.KingsIsle.com


-----Original Message-----
From: ravi [mailto:[email protected]] 
Sent: Monday, April 09, 2012 5:56 AM
To: [email protected]
Subject: Re: Strange 'pause' activity during testing

I disabled iptables and ip6tables.
But still I am seeing this issue only on linux.

Can you let me know if there is anything else I need to do.


Thanks





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to