You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/06/22 15:43:45 UTC

DO NOT REPLY [Bug 20998] New: - Assertions and RegexExtractor don't handle null responseData

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20998>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20998

Assertions and RegexExtractor don't handle null responseData

           Summary: Assertions and RegexExtractor don't handle null
                    responseData
           Product: JMeter
           Version: 1.9.RC2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: tjsb@slb.com


If a sample does not return any responseData at all (i.e. the response data is 
null), the all the Assertions (apart from Duration) and the RegexExtractor 
throw NullPointerExceptions which seem to cause the affect samples to be lost.

One way to get round this is to treat null responseData as an empty byte array.

However, should Assertions treat a null response the same as a zero-length 
array? Or should there be a new Assertion error message to report that the 
data is missing?

In the case of RegexExtractor, should (.*) match the empty response?

Either way, it would be useful to fix the current behaviour so that the test 
does not lose the samples. [Note that other samples are not lost].

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org