Text frame filter fails to discard some frames on high load

[Former user]

Hi Peter,

I am using the text frame filter with regular expression and it seems to filter out text frames just fine, if the no of threads is not high. However, as the number of threads are increased, it fails to filter out some of the frames that match the regex and would usually be filtered out on low load. As a result of this, close connection sampler reads this frame as a response instead of close connection response which it expects and hence, fails with this message: Response message: Websocket error: received not a close frame, but Text frame with text "<text frame>"

Can you somehow find out what is the cause of this and fix it?

[Peter Doornbosch]

Hmm, weird...

[Peter Doornbosch]

I cannot reproduce this. Are you sure that failing matches are indeed incorrect? Isn't your server sending different messages than you expect under high load?

If you are sure this is a bug in the plugin and want me to investigate, i need more information. You can mail me, so you don't have to share all the details with the whole world.

[Peter Doornbosch]

Added synchronisation on setting frame filters, could you please try again?

[Peter Doornbosch]

Closed, because not reproducible.