I cant run it in GUI mode....its a remote server... so can run it only in non-gui...thats the only access i have...
I ran the test..and there was no resposne after the first 2 statements and so i killed it... Later again i ran and left it... this time it completed...in both the cases it was only 1 thread 1 loop but the response was.. 1179302167758,224633,HTTP Request,Non HTTP response code,Non HTTP response message,Thread Test 1-1,text,false I am trying to figure this one out...Any idea??? Regards On Wed, 16 May 2007 sebb wrote : >Does it work OK in GUI mode? > >How long did you wait before considering it as stuck? > >What is the test doing? > >Note: please don't post the test plan to the mailing list; a brief >description will do. > >Or you could create a Bugzilla issue and then attach the file there >(conceal any sensitive information first) > >Or send me the JMX privately, and I'll see if I can find out what the >problem is. > >S. >On 16 May 2007 06:17:07 -0000, Aneesh K raj ><[EMAIL PROTECTED]> wrote: >>Hi, >> >>I am running a test from command line .. >> >> >>jmeter -n -t E2RemoteTestUnix.jmx >> >>Created the tree successfully >>Starting the test >> >> >>thats it ..its getting stuck...What could be the problem...I want to find the >>cause..Any logs ....that can help me.... >> >>I tried jmeter.log but..it wasnt useful... >> >> >>In the logs...the last few statements were... >> >>2007/05/15 22:58:34 INFO - jmeter.engine.StandardJMeterEngine: Starting 1 >>threads for group E2 Test. Ramp up = 1. >>2007/05/15 22:58:34 INFO - jmeter.engine.StandardJMeterEngine: Continue on >>error >>2007/05/15 22:58:35 WARN - jmeter.threads.JMeterThread: >>jmeterthread.startearlier=true (see jmeter.properties) >>2007/05/15 22:58:35 INFO - jmeter.threads.JMeterThread: Thread E2 Test 1-1 >>started >> >> >>Thanks & Regards >>
