Thanks Sebb.
The Java version and OS info you requested: Sun 1.4.2_02 on Linux: build 1.4.2_02-b03, mixed mode Red Hat Linux Advanced Server release 2.1AS (Pensacola) The server itself is a VMWare virtual running on VMWare ESX server. We do need XML logs instead of CSV as our test suite parses the XML to build a nightly test report... I understand the XML logs have more options to capture data - is this correct? I'll push for an upgrade to an updated JMeter version to see if it fixes this issue - however this fault is intermittent, and surfaced only recently after we've used 2.1.1 a long time. > > Since the automated script runs other tests subsequently, the > > 'jmeter.log' gets overwritten - is it possible to specify a unique > > jmeter.log file on the Jmeter command line? > > The -l flag names the output - see in jmeter-n.bat for an example usage We already use the -l parameter to capture the XML format logfile. Here's a sample command line JMeter invocation as executed by the automated test suite (it's a mouthful): -------------------------------------------------------- ../support/jakarta-jmeter-2.1.1/bin/jmeter -t b2b/cxml1.2_platform_OSN/outgoing_inv/cxml1.2-platform-OSN-inv.jmx -l ../log/2007-09-05_17-27-11_1276/1_b2b-cxml1-2-platform-OSN-outgoing-inv- cxml1-2-platform-OSN-inv-jmx_1276.log -p ../log/2007-09-05_17-27-11_1276/testrun.cfg -Dfile_format.testlog=2.0 -------------------------------------------------------- A jmeter.log file is generated in addition to the '...inv-jmx_1276.log' file named in the invoke above. It logs any JMEter exceptions generated in the test run, and is saved in same directory as invocation was made in. Subsequent test runs overwrite the old file and I was hoping to make it unique and save it in the same directory above so I could view any JMeter exceptions thrown during the test. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-93350725, Email: [EMAIL PROTECTED] -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 September 2007 6:20 PM To: JMeter Users List Subject: Re: Intermittent truncated logfile - non-GUI mode On 05/09/07, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Hello - > > > > Just requesting help with a strange intermittent failure in JMeter. > > > > Every few days, a JMeter testcase (always the same testcase) run by an > automated script in non-GUI mode fails -- the JMeter process exits > normally, but the logfile generated only has these first two lines: > > <?xml version="1.0" encoding="UTF-8"?> > > <testResults version="1.1"> > > > > When the test works, the logfile looks like this: > > [EMAIL PROTECTED] 2007-09-05_12-10-34_21860]$ cat > 1_b2b-monitoring-monitor-for-c1OR-hangs-jmx_21860.log > > <?xml version="1.0" encoding="UTF-8"?> > > <testResults version="1.1"> > > > > <sampleResult timeStamp="1188958246540" dataType="text" > threadName="Integration Test Thread Group 1-1" label="Invoke the handler > URL " time="237" responseMessage="OK" responseCode="200" > success="true"><assertionResult failureMessage="" error="false" > failure="false"/></sampleResult> > > </testResults> > Unless you really need the result to be in XML, it could be worth trying CSV output. > > We're using JMeter 2.1.1? The automated runs occur on a VmWare instance > which has a fair bit of memory (never swaps). 2.1.1 is rather old. > Can anyone help? It looks to be a bug either in JMeter or in Java. Which version of Java? OS? > > Since the automated script runs other tests subsequently, the > 'jmeter.log' gets overwritten - is it possible to specify a unique > jmeter.log file on the Jmeter command line? > The -l flag names the output - see in jmeter-n.bat for an example usage > > Kind regards, > > Sonam Chauhan > > -- > > Corporate Express Australia Ltd. > > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
