Compatibility issue with Azure Load Testing

Hi

We are trying to use JMeter with the jmeter-websocket-plugin within Azure Load Testing and are finding some inconsistencies in error reporting. We have some WebSocket request-response Sampler_s passing to a _WebSocket Text Frame Filter to filter out the messages that we aren’t interested in. This works fine in the JMeter GUI, but through Azure Load Testing all of the discarded messages are flagged as errors with a label of PARENT_SAMPLER_NAME-n

For example, this is shown in the results CSV file as:

Request-Response Sampler    200 OK
Request-Response Sampler-0      Received Text frame with text
Request-Response Sampler    200 OK
Request-Response Sampler-0      Received Text frame with text
Request-Response Sampler    200 OK
Request-Response Sampler-0      Received Text frame with text
Request-Response Sampler    200 OK
Request-Response Sampler    200 OK
Request-Response Sampler    200 OK
Request-Response Sampler    200 OK
Request-Response Sampler-0      Received Text frame with text
Request-Response Sampler-1      Received Text frame with text

A second issue that we are seeing is where we have a WebSocket SIngle Read Sampler configured with the Optional Read box selected and we see responseCode=No response, responseMessage=Read timeout, no message received in the results CSV,yet Azure Load Testing is marking these as errors when I’d expect them to be ignore (because the Optional Read box is checked).

We are using JMeter 5.6.3 and jmeter-websocket-plugin 1.2.10

Could you please confirm if this behaviour is as expected, or if there is an incompatibilty between the plugin and Azure Load Testing

Thanks

Comments (3)