https://issues.apache.org/bugzilla/show_bug.cgi?id=52345
Sebb <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Sebb <[email protected]> 2011-12-16 16:10:49 UTC --- (In reply to comment #2) > Hey Sebb, > > Thanks for your quick response. > I tried running the JMX script separately in non-GUI mode on each server but > still getting similar kind of issue. Then the problem is nothing to do with JMeter distributed mode, is it? > Even I tried running my JMX script using JMeter 2.5.1 but problem still > persists. > > Other Options I tried was.. > I copied the JMeter folder on one of the Application Server node and running > my > load test from App server in non-GUI mode hitting directly the same App > server. > Thinking there could be network latency. But still I see very high response > times in the JTL file continuously for some time. Again, distributed mode is irrelevant. > I am using SPLUNK to get the results from my JBoss access log. In splunk my > application response times are below 1 second. But when it comes to JMeter > output file, it shows very high response times. > > We are running the test on Amazon EC2 where JMeter Client and servers are of > large instances. There's absolutely no evidence here that JMeter distributed mode is at fault, or indeed JMeter. Bugzilla is not a suitable place to continue this discussion. Please subscribe to the JMeter user list and post there. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
