Hello - I am working off the Dec 29 2003 build. JMeter seems to handle
errors differently in GUI and non-GUI mode. My JMX has a single thread group
(5 threads). It is set to 'Stop Thread' when a sampler has an error.
When I run the JMX graphically, only the single thread with the error is
stopped -- the other threads continue to run. However, when run in non-GUI
mode (I use the "-n" switch) the entire test run is stopped on the first
error. Details of the test run are below.
This is the test being run in non-GUI mode:
-----------------------------------------------------------
$ jmeter -t oci.jmx -p cetest.2004-01-05_21-32-04.properties -l sonam.log -n
Created the tree successfully
...
-----------------------------------------------------------
After the run, there is only one entry in 'sonam.log':
-----------------------------------------------------------
<sampleResult timeStamp="1073342379697" dataType="text" threadName="Regular
OCI
login1-1" label="Login" time="1062" responseMessage="Non HTTP response
message"
responseCode="Non HTTP response code" success="false"/></testResults>
-----------------------------------------------------------
In GUI mode only the one thread stops. The rest work fine:
-----------------------------------------------------------
$ jmeter -t oci.jmx -p cetest.2004-01-05_21-32-04.properties
[Full GC 38817K->6096K(249088K), 0.2978116 secs]
-----------------------------------------------------------
Two more observations:
1) The jmeter.properties file is ignored when a property file is used at the
command line ("-p").
2) The logfile switch is ignored in *GUI* mode. (No logfile is generated
"-l" is invoked without "-n").
With regards,
Sonam Chauhan
--
Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED]
