Forum Discussion
SmartBear_Suppo
13 years agoSmartBear Alumni (Retired)
Elvorin wrote: 1. I've set a test case with fixed rate generator. It's supposed to generate 25/sec, with burst size 25 (tried 1 too). But it doesnt send that many requests per second.
3. Requests/sec graph shows it going down from 25 to 1 or 2 within few seconds.
The Fixed Rate Generator is almost certainly generating 25/sec if that's what you set it to. You can check this by connecting the generator directly to a Table Log.
However, it seems that your soapUI Runner starts sending requests as it gets trigger messages from the Generator -- but since the requests doesn't complete very fast (maybe
because of the ConcurrentModificationException?), the runner starts queuing trigger messages up and eventually also discarding them. These mechanisms are explained here in the documentation.
Elvorin wrote: 2. It starts throwing error pretty soon saying 'java.util.ConcurrentModificationException: Document changed during select'. I have property transfer from the response in my test case, for logging purposes. That is causing the failure (confirmed by enabling/disabling that step).
The question is to where you transfer the property. Each virtual user (or trigger message) in a soapUI Runner gets its own copy of the soapUI TestCase -- but not of the entire TestSuite or Project (that would be way to heavy for any computer to run). Thus, TestSuite and Project properties are shared between Virtual Users, and will cause concurrent issues if you don't avoid writing to them concurrently. Read more about this here.
Hope this helps!
Henrik
SmartBear Software
Related Content
- 11 months ago
- 2 years ago
Recent Discussions
- 2 days ago