I have a server, it uses the following regular expression to determine the end of a "transmission" from a client:
.*End\":[0-9]{3}}]}\r\n
This works exactly as expected when a normal client connects. Has done for over a year now.
I've decided to start doing some load testing using Apache JMeter, I've done a couple of simple tutorials and managed to successfully run some http tests.
However, when I try running a TCP Sampler against my own server, the server doesn't recognize the above pattern from the string it is sent by JMeter.
This is despite the fact that the String JMeter sends is an exact copy of a string it accepts every time when coming from an actual client.
The server's debug messages say that a match wasn't found and the message is incomplete, then it waits for more information from JMeter.
I experimented by removing the \r\n
from the regex pattern and the JMeter test string and the server successfully recognized the end of the message from JMeter.
Anyone got any suggestions on how to solve this? It seems like some sort of character encoding issue perhaps?
\r\n
in the JMeter message the server still doesn't recognize it. – mal