Forum Discussion

NSeibert's avatar
NSeibert
Contributor
14 years ago

Relationship between generators and data source.

Have an answer on how to use a data source with loadui here (viewtopic.php?f=10&t=7441)

After initial setup.. what I am noticing

If I set up a test to run against a datasource of 1000 records, the default settings (for the most part) seem to iterate through all of the records in the data source.

BUT.. If I alter the loadUI Generator (fixed load) to a larger interval, then the data source seems to no longer iterate. I get only the first record for each request.. http://website/user1?report=1000

How can I determine the relationship between datasource records and the generator?

Is there a way to preseve or 'placehold' the data source (increment at the next interval) no matter what the interval?
  • Hi,

    I'm not able to reproduce this. As long as the DataSource is set to be shared, and to restart (the two first checkboxes in the configuration), you should be getting all the different values of the DataSource, regardless of the rate of requests.

    Regards,
    Dain
    eviware.com
  • Hello again and thanks for the video explanation!

    After watching the video, we've concluded two things:
    • You seem to be using the Fixed Load Generator incorrectly. It's supposed to be connected as shown in the first screenshot here. The Interval should be the only delay control you need (no need for separate Delay Component). What are you trying to achieve?

    • Still, it looks like you might have found a bug. It's hard to tell exactly what's going on though. Is it possible for you to e-mail your loadUI project, soapUI project and XLS-file to support at eviware.com?


    Regards!

    /Henrik
    eviware.com
  • Thanks for the e-mail. It helped us discover a quite nasty bug.

    Would you mind trying the latest nightly build in a few hours?

    EDIT: Actually, the build server was down. Stay tuned.

    /Henrik
    loadUI team
  • This is fixed! Pulled the new loadui build down and reran the original scenario, incrementing is keeping track of the previous run. Looks like this bug is exterminated!!

    Henrik the bugslayer! Thanks for the help.
  • I think I spoke too soon. When I went further trying to attach a JDBC datasource, something came loose.
    I am no longer able to get ANY of my loadUI > soapUI runners to fire.

    See the here for an illustration
    > http://goview.com/?id=1b966467-52db-40b ... 874f045334.

    Thank you for any suggestions on what might be causing this disconnect.
  • After fiddling around a bit I was able to resurrect the original successful pairing, I recant looks like a 'meatware' issue, misuse of setting the test case between distributed mode and local mode. The third part of this is how to then wrap the case here up into a distributed load test and the JDBC data pool configuration. Another thread.