Yes, this is a known bug 43584. This has been fixed in SVN. +Assertion fixed messages don't contain commas +CSV files now support embedded delimiters.
In the meantime, I'm afraid you'll need to edit the CSV files. On 13/05/2008, Steve Kapinos <[EMAIL PROTECTED]> wrote: > Previously I had jmeter save several logs including the Aggegrate Report > to files and I would reload those files in jmeter to help visualize the > results. > > Since adding an duration assertion test to my testplan, I can no longer > load the resulting files in jmeter to read them. Looking closer, it > appears to be because the assertion result includes commas. My files > are being written to csv for performance benefits as recommended in the > documentation. > > Example > > 05/13/08 12:04:11,18578,List Conferences,200,OK,Monitoring Thread > 5-1,text,false,The operation lasted too long: It took 18,578 > milliseconds, but should not have lasted longer than 10,000 > milliseconds.,1047,1,1 > > When you try to load the resulting log file into jmeter, it errors and > says look in the log file. > > Log just says > > 2008/05/13 12:10:16 WARN - jmeter.save.CSVSaveService: Error parsing > field 'Latency' at line 17 java.lang.NumberFormatException: For input > string: "578 milliseconds" > 2008/05/13 12:10:16 WARN - jmeter.reporters.ResultCollector: Problem > reading JTL file: > D:\Projects\Tandberg\tms\Tests\LoadTests\EventHandling\monitor-out\overa > ll.txt > > > --------------------------------------------------------------------- > 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]
