https://bz.apache.org/bugzilla/show_bug.cgi?id=64183
Felix Schumacher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID --- Comment #5 from Felix Schumacher <[email protected]> --- OK, this would have been a really good question for the users mailing list. The problem with your testplan is, that you are generating beanshell fragments with the JMeter functions, that then get run by beanshell. If you look at the failed samples, you will notice, that they include those strings that start with a number and continue with a character or they include an invalid octet number (those that start with a zero and contain a 8 or 9 digit). If you want to generate valid code, you have to add quotes around the JMeter function and you might prefix it with a return to make the statement a bit clearer. You should switch to groovy for the language instead of beanshell, as it is more powerful and sane in the supported features. But doing so, you will stumble upon the next speciality of JMeter (together with compilable scripting languages), which is, that you either will run out of memory (the script will be compiled every run), or you will not get a random value on each run (the first compiled script will be cached). If you are using a scripted sampler, you should use the languages features to achieve your goals. The functions are meant for those places, where you don't have the power of the scripted languages. Every follow up to this answer should really happen on the mailing list. -- You are receiving this mail because: You are the assignee for the bug.
