Indeed, user defined variables should not be used with functions that generate different results each time they are called. User parameters doesn't really help but I will use another way. Thanks anyway.
On Sun, Mar 11, 2012 at 7:02 PM, Deepak Shetty <[email protected]> wrote: > I didn't realize you were using this in user defined variables. Thread num > function doesn't work there -check docs. Use user parameters instead > On Mar 11, 2012 10:58 AM, "Cyril SANTUNE" <[email protected]> wrote: > >> So I try: >> - ${__threadNum()} => the result is : StandardJMeterEngine >> - __threadNum() => the result is : __threadNum() >> - ${__threadNum} => the result is : StandardJMeterEngine >> - __threadNum => the result is : __threadNum >> >> It's maybe impossible to use threadNum in this case. >> >> >> >> On Sun, Mar 11, 2012 at 6:50 PM, Deepak Shetty <[email protected]> wrote: >> > __threadNum () >> > On Mar 11, 2012 10:37 AM, "Cyril SANTUNE" <[email protected]> >> wrote: >> >> >> >> Hi, >> >> I have something like that in 'user defined Variables' >> >> ---------- >> >> curl --output /tmp/${__threadNum}.tmp ftp://${server_ip}/read/10MB.bin >> >> ---------- >> >> ${server_ip} was correctly replaced, but the threadNum was not. It was >> >> replaced by 'StandardJMeterEngine' >> >> >> >> Should I use another syntax in this case ? >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
