It actually seems to have a negative impact too, that thread ends right away.

On more testing if I don't set the

group.setScheduler(true);

and hence don't get into the following code (in my NewStandardJMeterEngine that extends StandardJMeterEngine)

thread.setEndTime(group.getDuration()*1000+(thread.getStartTime()));

then test takes the values from the .jmx file and runs as per those properties.

Deepak

Deepak Batra wrote:

thread.setEndTime(group.getDuration()*1000+(thread.getStartTime())); doesn't seem to have any impact. I have a controller that sets this duration but my test just ignores this values and starts and ends right away.

Can someone guide what I am doing wrong.

Deepak

---------------------------------------------------------------------
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