On 08/12/2009, Ronan Klyne <[email protected]> wrote:
> sebb wrote:
>
> > On 08/12/2009, Ronan Klyne <[email protected]> wrote:
> >
> >
> > > sebb wrote:
> > >
> > >
> > > > On 08/12/2009, Ronan Klyne <[email protected]> wrote:
> > > >
> > > >
> > > >
> > > >
> > > > > Hi all,
> > > > >
> > > > >  I've just started seeing a JavaScript error in jmeter.log when I
> try to
> > > > >  start a test.
> > > > >
> > > > >  I use JavaScript in many parts of my test script, and I have looked
> at
> > > > >
> > > > >
> > > >
> > > the
> > >
> > >
> > > >
> > > > > recently changed ones for obvious errors - none found.
> > > > >
> > > > >  The error is only hinted at by this traceback:
> > > > >
> > > > >  2009/12/08 14:35:42 ERROR -
> > > > > jmeter.engine.StandardJMeterEngine: Uncaught
> exception:
> > > > > org.mozilla.javascript.EvaluatorException: missing
> )
> > > > >
> > > >
> > > >
> > >
> >
>  <snip />
>
> >
> > >
> > > > The above line is probably the location of the call.
> > > >
> > > > Thread Group - Ramp Up.
> > > >
> > > >
> > > >
> > > >
> > >  All of those are of this form:
> > >
> > >  ${__javaScript(2*${ramp_up_secs_per_thread})}
> > >
> > >  Is it allowed to nest the '${}' construct in this way?
> > >
> > >
> >
> > Yes.
> >
> > The error message suggests you may have used:
> >
> > ${__javaScript(2*${ramp_up_secs_per_thread}}
> > or
> > ${__javaScript(2*${ramp_up_secs_per_thread}})
> >
> > by mistake, i.e. misplaced ')'
> >
> >
> >
>  I've checked all my thread groups, and they all have the correct syntax :-s
> ...
>
>  Since it was the only thing in that broken expression, I tried changing
> "ramp_up_secs_per_thread" to be some integer constant, and everything
> works...
>
>  This variable is currently set in the test plan to be
> "${__P(ramp_up,__javaScript(${dev_mode}?0:5))}"
>
>  Does that look OK?

No, because the default for ramp_up is the string
"__javaScript(${dev_mode}?0:5)"

If you want the default to be a function, you need to use the ${} wrapper, i.e.

"${__P(ramp_up,${__javaScript(${dev_mode}?0:5)})}"

>   # r
>
>
> ---------------------------------------------------------------------
>  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]

Reply via email to