ContributionsMost RecentMost LikesSolutionsRe: SoapUI 5.5.0 will not run project or suites - Toolkit not initialized error I cannot see any problems with test cases or suite as on my picture. Do you have any details or a project that can reproduce the problem? Environment may be a key as well. I'm using win 10 to check. Re: LOAD UI Pro - Server Monitoring for UNIX Solaris Please check that all the objects that you're interesting in are available to any SNMP client tool. I suspect that the problem is in rights but it may be a different reason. LoadUI will see the once you'll set up your server. Re: Reg: LOADUi with data Driven testing It is possible to use datasources in SoapUI tests. Additionally it will be possible to use shared datasource option in load test. It will allow each virtual user to use its own record. Re: How to increase log level in LoadUI-NG remote agent Any problems with agents should be posted to Ready!API or agent console logs. I could recommend you to contact support and provide your logs to them. Re: LoaduI Clod agent This is the only information we could receive via amazon api. So i could only suggest you to check if the string is not contains any spaces or other non key symbols. Re: Running All Load test using the Command-Line Could you contact support with a sample project? Re: Is it possible to list all the test cases/targets in all scenarios in LoadUI NG Pro startup script? It's not possible to access all the targets from the load test script yet. I hope to improve this in one of the next releases. But you could do anything you want with the current functionality. You could use events and setup of the test case in beforeTestCase. LoadUI context could be used as a global storage and SoapUI context could be used as a virtual user storage. And the shared datasource thing is not working the way you described it or at least i did not understand this correctly. Each time test step requested a new line shared datasource returns the next one. Its not isolated anyhow. It became a global object available for each virtual user. It'll be probably much easy to understand it's work via logging data in afterTestStep loadUI event. Re: Setting for endpoint dns cache Are you using the same set of names for old and new server set? What about addresses? Are they the same and unique from session to session? I mean could you just check an IP of the first set in order to switch to another one if first one became unavailable? Re: Setting for endpoint dns cache LoadUI part is not controlling any system caches in any way. In general it's not clear how dns could be related with availability of the server. You could use IP addresses and forget dns. But i think dns is not a real bottleneck in your situation. Re: MEMORY LEAKS, non suitable for load tests! I've attempted to reproduce memory leaks with an attached project without any luck. The problem could be in groovy scripts itself. I could check another script if you have one. Are you having any problem with this exect script? Could you modify it so it'll have any problmes you're mentioning?