Summary: | Proxy inserts "${}" before each character in every string recorded. | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Achim Westermann <achim.westermann> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | geoboy88 |
Priority: | P2 | ||
Version: | 2.3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
URL: | http://www.k-plus-s.com | ||
Attachments: | screenshot of recorded samples |
Description
Achim Westermann
2008-06-13 01:22:12 UTC
The comman "set HEAP=-Xms256m -Xmx1024m" in jmeter.bat shows the same result. The java process takes up to 1 GB. In the proxy settings of JMeter the checkbox "regex matching" had to be checked or nothing would be recored, even if the browser used the JMeter proxy (stopping it would cause the browser to fail getting a response). Regex matching has nothing to do with the proxy recording itself. It only affects how the requests are processed when replacing variables. Have you defined any variables on the Test Plan? It looks like the variable replacer has been confused by something. Hi Sebb, I narrowed it down a bit. I did not define any variables. I found out that this happens when my Thread Group has a "View Result Tree" Listener attached while recording. If I remove it, recording works fine. So: - Add a Thread Group - Add a Proxy to the workplace. Change nothing but port to 9090 (should not matter) and select the Target Controller "testplanname -> Thread Group. - Add a Listener of type "View Result Tree". - Start the proxy. - Point your browser to localhost:9090 in proxy settings. -> After clicking the first link, cpu load rises and after approx. 20 seconds on a core 2 duo 2GHZ, 2GB RAM the 1 GB limit is reached and you should get the exception. kind regards, Achim Just tried that, and it works fine for me when testing against www.apache.org, Google and BBC news. Does it happen to you for these sites? Or only some sites? Are you still using the JMeter command-line proxy settings? If so, can you try it without? BTW, if you want to see the pages as they are recorded by the proxy, add the listener to the proxy server. Thanks for your patience. This time I took more time to isolate the error. It seems to be as you said in first place. - Just click the add button in the top - level test plan. A user defined var is created. Leave it empty. - Now start the proxy session. Record to a Thread group. --> The error should occur. - This happens also when starting JMeter without proxy settings (had to test with localhost tomcat). kind regards, Achim I just spent a long and frustrating day debugging my script to find this bug: ${} insertion and "out of memory" error. Please fix this bug! Thanks a lot! This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2125 |