FYI conversion is done like so in the BSF PreProcessor (child of While
Controller) using javascript language:
vars.put( "upcTotal", props.get("upcTotal") );

On Mon, Mar 19, 2012 at 11:58 PM, Pulkit Singhal <[email protected]>wrote:

> Worked around the problem by adding a BSF PreProcessor as a child of the
> While Controller in order to convert the JMeter Property into a JMeter
> variable.
>
> So instead of:
>
> ${__javaScript(${upcCounter}<=${__P(upcTotal)})}
>
> I now use:
> ${__javaScript(${upcCounter}<=${upcTotal})}
>
> But still that's a rather contrived workaround.
>
> Can anyone answer why: JMeter Properties not evaluate-able in logic
> controllers?
>
>
> On Mon, Mar 19, 2012 at 11:19 PM, Pulkit Singhal 
> <[email protected]>wrote:
>
>> Changing the condition from:
>>
>>
>> ${__javaScript(${upcCounter}<=${__P(upcTotal)})}
>>
>> to something like:
>>
>> ${__javaScript(${upcCounter}<=10)}
>>
>> helps narrow down the problem to the following chunk of code:
>>
>> ${__P(upcTotal)}
>>
>> So are JMeter Properties not evaluate-able in logic controllers?
>>
>>
>> On Mon, Mar 19, 2012 at 12:10 PM, Pulkit Singhal <[email protected]
>> > wrote:
>>
>>> 1) The data that I need to access is present in JMeterProperties (comes
>>> from a different thread group - consecutive excution):
>>>
>>> upcArray_1 = 012934023423
>>> ...
>>> upcArray_10 = 342034234233
>>>
>>> Therefore the foreach controller does not work for me as it tries to
>>> find the prefix (upcArray) in the JMeterVariables which is not the right
>>> place to look for it.
>>>
>>> 2) So I am attempting to add a counter as the child of the while
>>> controller to let me loop through the data in the JMeterProperties:
>>>
>>> WHILE CONTROLLER
>>> Condition: ${__javaScript(${upcCounter}<=${__P(upcTotal)})}
>>>
>>> CHILD COUNTER
>>> Start: 1
>>> Increment: 1
>>> Reference Name: upcCounter
>>> Track Counter Independently for each user - YES
>>>
>>> 3) But it counts 1 then 2 and then its stops! It doesn't go all the way
>>> up to 10 ... what am I doing wrong here?
>>>
>>
>>
>

Reply via email to