On 07/11/2008, Fitzpatrick, Adrian <[EMAIL PROTECTED]> wrote: > > Hi, > > I've seen a similar problem with CSV results files. As you are using XML > files, I don't think your having the same issue but it might point you in the > right direction. The problem we have was that we had assertions in our script > and the result text for the assertion was included in the JTL file. However, > this text actually had a comma in it. So, when we tried to re-open the JTL > file in JMETER, the comma from the assertion text was treated as a delimiter > for the CSV and hence the file couldn't open. > > I know this specific problem has been fixed in the latest verison of Jmeter, > but perhaps your having a similar one - maybe some XML control characters in > the file where they shouldnt be. Can you open the file in an XML editor to > see if its valid XML?
The XML is created by the same library that reads it so it's extremely unlikely that the output is invalid. > Also, what does the JMETER log file say when you try to open this file? > > Finally, I dont think size is your issue - we have JTL files that are several > 100 MB in size and can open these without issues (cept its a bit slow!) Unfortunately XML files are currently processed all at once (this needs to be fixed). Use CSV output instead. There was some discussion on the user lists as to how to convert XML to CSV using scripting languages or XSLT. > - Adrian > > ************************ > > This message has been delivered to the Internet by the Revenue Internet > e-mail service (OP) > > ************************* > > > --------------------------------------------------------------------- > 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]
