https://bz.apache.org/bugzilla/show_bug.cgi?id=66265
Felix Schumacher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Felix Schumacher <[email protected]> --- To answer your question, no, I don't know a way to ignore those lines. But, I think this error can be avoided altogether, when you stop to use the ${...} JMeter feature on JSR223 (or specifically Groovy) scripts. The reason to not use it: 1) It is not needed in Groovy code 2) JMeter will use the ${...} like a template to generate the actual JSR223 code and use it for compilation/interpretation. If the code stays the same throughout the test, the cache is more effective and uses less RAM 3) It is confusing, as Groovy uses the same syntax for variable interpolation And you omitted an exception, that you will likely have received in the log files. __counter is a function, that has to be called with a parameter. A combination of those things lead the the exception. You can pass the threadNum as a parameter/argument to the sampler and get rid of the templating for threadNum. Same can probably done for counter (using it with a parameter). That can be combined with log format strings to log.info("DEBUG: A: {}-{}", args[0], args[1]); Add "${__threadNum} ${__counter(TRUE)}" to the "Parameters" field to fill the args variable. -- You are receiving this mail because: You are the assignee for the bug.
