Thanks Sebb. I found the problem - we were been already using the '-p <property_file>' parameter for parameters used by our parameterized test scripts. This meant Jmeter ignored it's property file, which were OK till 2.1.1 gained a new "file_format.testlog=2.0" setting. Hence I added "-Dfile_format.testlog=2.0" to our invocation.
Yes, I see the NPE in jmeter.log. I had put up documentation on the 1.9.1. log format on the wiki (LogAnalysis section) earlier. Once I finish, I'll add documentation on the default 2.1.1 log format (file_format.testlog=2.0). Do correct any fault in my assumptions below: > --------------------- > <sampleResult timeStamp="1144217221253" ...><assertionResult > ...></sampleResult> > --------------------- > This resembles the old log format, but has different nested elements: > - The old practice of representing 302 redirects as <sampleResult> > subelements is gone. > - New <assertionResult> subelements now occur under <sampleResult>. A comment regarding the new log format: From what I understand, the new log format will use <httpSample> for the HTTP sampler and <sampleResult> for the JDBC sampler. Just from a automated log processing point of view, having uniform <sampleResult> element for all log entries is more predicatable. Alternatively, where specialized elements like <httpSample> are used, some documentation on the special elements (perhaps a DTD?) would be needed to properly process logs. On another topic - can JMeter be set to stream results / log entries to another application as testing occurs (as opposed to processing the log file when tests complete). This other application could be, say, a generic testing engine (as in our case), syslog, a system management framework, etc. I was browsing some entries in jmeter.properties and came across these entries for JMeter 'remote testing' below. Is it possible to easily adapt JMeter remote testing to stream results to another application? What protocol do the master and remote servers use to communicate with each other? ----------------------------------- # Remote batching support # default is Standard, which returns each sample # Hold retains samples until end of test (may need lots of memory) # Batch returns samples in batches # hold_samples was originally defined as a separate property, # but can now also be defined using remote.mode #mode=Standard #mode=Batch #mode=Hold #hold_samples=true #num_sample_threshold=100 #time_threshold=60000 ----------------------------------- Sincerely, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED] -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Thursday, 6 April 2006 11:21 AM To: JMeter Users List Subject: Re: log file formats - upgrade problem On 05/04/06, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Hi - regarding the new logging format, I looked in jmeter.properties > and found this directive: > 'file_format.testlog=2.0' > The comments indicate this is set to '2.0' so that logs are written in > the old log format. > > A simple test plan with these 2 elements: > 1. JDBC sampler > 2. HTTP sampler > ...mormally generates entries of this nature: > --------------------------------------- > <sampleResult ... label="JDBC Request" ...> > <sampleResult ... label="HTTP Request" ...> > --------------------------------------- > > When I comment out that property (to use the new log format), JMeter > switches to the new format, but the logs for the JDBC sampler go > missing: > --------------------------------------- > <httpSample ... lb="HTTP Request" ...> Check jmeter.log - you will probably find an NPE error; this causes the sample to be lost. > --------------------------------------- > > Am I doing this correctly, or is the new log format not ready yet? There's always room for improvement; indeed I hope that if you try the current nightly you will find that the NPE error at least has been eliminated. > Sincerely, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED] > > -----Original Message----- > From: Sonam Chauhan [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 5 April 2006 5:08 PM > To: JMeter Users List > Subject: log file formats - upgrade problem > > Hello JMeter list! I'm in the process of upgrading a testsuite from > JMeter 1.9.1 to 2.1.1 and ran into problems below in how log files are > processed. Can you help? > > > JMeter 1.9.1 > ============================ > The old JMeter (1.9.1) used to generate logs of this type: > --------------------- > <sampleResult timeStamp="1144219416885" ...> > </sampleResult> > --------------------- > > > 'Old Tests' in JMeter 2.1.1 > ============================ > When an 'old' JMeter testscript (i.e. created using JMeter 1.9.1) is run > in the new JMeter (2.1.1), logs of the following type are generated: > --------------------- > <httpSample t="422" lt="422" ts="1144219352620" ...> > <assertionResult> > <failure>false</failure> > <error>false</error> > </assertionResult> > </httpSample> > --------------------- > > > 'New Tests' in JMeter 2.1.1 > ============================ > However, if I build a new testcase from scratch new JMeter (2.1.1), it > generated yet a different log format: > --------------------- > <sampleResult timeStamp="1144217221253" ...><assertionResult > ...></sampleResult> > --------------------- > This resembles the old log format, but has different nested elements: > - The old practice of representing 302 redirects as <sampleResult> > subelements is gone. > - New <assertionResult> subelements now occur under <sampleResult>. > > > Questions: > =========== > 1. How could I make both old and new test scripts generate the same > log format when run in JMeter 2.1.1? > > 2. Is there documentation on the JMeter 2.1.1 log format? > > Sincerely, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-9335-0725, 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]
