On 10/09/2007, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Thanks a lot Sebb! I hope to give 2.3 a whirl soon. > > We actually run the automated tests from the same directory, but create > unique log directory for each JMeter invocation. You made a good point > of cd-ing to the unique log directory - thanks! It's also good to know > 2.3 has the new -j option. > > > The file_format definition could be in testrun.cfg or > > jmeter.properties if it is always the same. > > The testrun.cfg file is rewritten according to the flags passed in at > runtime, but my impression was that (in 2.1.1) when the '-p' option is > used, JMeter ignores the contents of jmeter.properties - is that > correct?
Yes, -p is used to override the default jmeter.properties file. You can also use the -q flag to define a secondary properties file - i.e. put commons stuff in jmeter.properties, and local changes in the -q file. You can also now define JMeter properties in user.properties. > Kind regards, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Thursday, 6 September 2007 12:34 PM > To: JMeter Users List > Subject: Re: Intermittent truncated logfile - non-GUI mode > > On 06/09/07, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > > 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? > > Yes, XML can capture more, because it is not restricted to single > lines of data, and can handle nested samples. > > But you may find that the CSV is enough, especially in the later > versions of JMeter. > > > > > I'll push for an upgrade to an updated JMeter version to see if it > fixes > > this issue > > Might be worth trying 2.3RC4 for one or two sample tests - please let > us know ASAP if there are any problems with the JMX files (they should > be upwards compatible - but scripts created in 2.3 won't run in 2.1.1) > > > - however this fault is intermittent, and surfaced only > > recently after we've used 2.1.1 a long time. > > That's a bid odd ... something must have changed ... but what? > > It's just occurred to me that it could be the same problem someone > else just reported - a NullPointerException in PrettyPrintWriter - > which is caused by some unexpected null data in the sample result. > This would not affect the CSV output, as the class is only used for > XML output. > > If you can get a stack trace, I could check the line numbers and see > if it's the same. > > > > > > > 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? > > Not with 2.1.1, although you can easily use a shell script to rename > it afterwards. > > 2.3RC4 (just out) has a new command-line option (-j) to name the file > - and the DOS scripts that take a test file have been modified to use > it (I'll try and remember to fix the shell scripts as well before 2.3 > final!) > > I hope to release 2.3 final before too long - assuming no > show-stoppers in 2.3RC4. > > > > > > > > > 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 > > The file_format definition could be in testrun.cfg or > jmeter.properties if it is always the same. > > 2.2 and later allow properties to be defined in additional files. > > Also now JMeter can run from a directory other than the bin directory, > so you could run it in the log directory to save quoting the full > paths. > > If you have a directory per test run that would solve your jmeter.log > problem too, but that's not necessary. > > ------------------------------------------------------ > > 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. > > See above. > > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
