On 10 January 2011 13:41, Adrian Speteanu <[email protected]> wrote: > Hello, > > I cannot open from GUI a .jtl file saved in CSV format (not even with the > same listener used to save it to disk). > jmeter 2.4
I don't think the settings are taken into account when loading from the GUI - perhaps they should be, but historically only the jmeter.properties settings are used. > This is in jmeter.log: > > 2011/01/10 15:20:20 WARN - jmeter.save.CSVSaveService: Error parsing field > 'timeStamp' at line 1 java.text.ParseException: Unparseable date: > "1293634840146" That looks like a timestamp in MS. Make sure that the jmeter.properties file is set accordingly: jmeter.save.saveservice.timestamp_format=ms This does not have a corresponding entry on the Listener Config page. Perhaps JMeter could check for "ms" format if the timeStamp does not parse, as it's unlikely to be confused with other formats. Also ensure that you either save the column header names in the CSV file, or ensure that jmeter.properties has the appropriate settings (see above). But it looks as that is OK, as the column name is correct. > 2011/01/10 15:20:20 WARN - jmeter.reporters.ResultCollector: Problem > reading JTL file: <actual .jtl file> > > Does anybody know if it was reported already? I've tried searching through > bugzilla and discussed topics and can't find anything about it. > > Also, does anybody know any quick workarounds? > > For the record, the configuration of what is saved on disk is : response > code, label, success, time stamp, csv field names, latency, elapsed, byte > count, > > Thanks. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
