Looking further at the stack trace shows that it is caused by a sub-sample with ResponseMessage=null.
[I was able to reproduce this by using BeanShell sampler to create a sample result, set the response message to null, and then add it as a subresult to the current sample. There may situations in which JMeter creates such subresults.] The XStream PrettyPrintWriter cannot handle null Strings, so I've updated the code in SVN to convert null to the empty string. This will stop the NPE in future. Meanwhile, if you disable writing to a file, and add a Tree View Listener (if necessary), you should be able to see which sub-sample is at fault by checking the Sampler Result tab - it will look like: Response Message: null if the RM is null. It would be useful to know what this reveals. On 05/09/07, Ronan Klyne <[EMAIL PROTECTED]> wrote: > Ronan Klyne wrote: > > It turned out to be due to a BeanShell Sampler doing: > > ResponseCode = -1 ; > > > > Ooops - disregard that - just a coincidence. > I'm a little pushed for time, and I'll try your suggestions tomorrow... > > # r > > -- > Ronan Klyne > Business Collaborator Developer > Tel: +44 (0)870 163 2555 > [EMAIL PROTECTED] > www.groupbc.com > > --------------------------------------------------------------------- > 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]
