Starting ReadyAPI 1.4.1 in our VM takes 5+ minutes...

Question

&nbsp;Hi,&nbsp;We've been using SoapUI Pro for a long time and have it as a standard part of our build process doing automated testing. We've got the execution of our Web Services test harness being done in a VM and whether I automatically or manually start ReadyAPI in that VM, it's taking over 5 minutes to start up the application! It's fully licensed and we only have this problem on the VM. Running it on my PC does not have the same problem.&nbsp;Any suggestions on what I can look for or check to work out why it takes so long? This is a MAJOR problem as we have 20 test suites, so we've losing over 100 minutes just in start-up time:(&nbsp;Thanks,Andy.

andyhore · Answer

&nbsp;I did just look in the ready-api.log file in my users .readyapi\logs folder and this is what I saw:&nbsp;2015-10-27 06:44:04,828 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:44:14,828 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:44:24,830 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:44:34,841 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:44:44,842 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:44:54,852 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:45:04,854 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:45:14,856 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:45:24,857 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:45:34,858 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:45:44,859 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:45:54,861 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:46:04,862 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:46:14,863 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:46:24,864 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:46:34,880 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:46:44,881 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:46:54,883 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:47:04,883 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:47:14,883 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:47:24,883 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:47:34,899 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:47:44,900 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:47:54,900 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:48:04,902 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:48:14,903 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:48:24,904 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:48:34,905 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:48:44,907 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:48:54,911 INFO&nbsp; [liquibase] Waiting for changelog lock....2015-10-27 06:49:07,678 INFO&nbsp; [Reflections] Reflections took 1312 ms to scan 1 urls, producing 487 keys and 1693 values2015-10-27 06:49:11,500 INFO&nbsp; [Reflections] Reflections took 3315 ms to scan 29 urls, producing 2166 keys and 8413 values2015-10-27 06:49:11,533 INFO&nbsp; [Reflections] Reflections took 15 ms to scan 2 urls, producing 75 keys and 160 values2015-10-27 06:49:11,579 INFO&nbsp; [Reflections] Reflections took 21 ms to scan 1 urls, producing 44 keys and 340 values2015-10-27 06:49:11,747 INFO&nbsp; [Reflections] Reflections took 134 ms to scan 13 urls, producing 341 keys and 1454 values2015-10-27 06:49:12,409 INFO&nbsp; [Reflections] Reflections took 641 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:12,743 INFO&nbsp; [Reflections] Reflections took 280 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:13,024 INFO&nbsp; [Reflections] Reflections took 266 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:13,341 INFO&nbsp; [Reflections] Reflections took 257 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:13,626 INFO&nbsp; [Reflections] Reflections took 259 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:23,920 INFO&nbsp; [Reflections] Reflections took 538 ms to scan 239 urls, producing 75 keys and 330 values2015-10-27 06:49:24,455 INFO&nbsp; [Reflections] Reflections took 534 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:26,077 INFO&nbsp; [Reflections] Reflections took 529 ms to scan 239 urls, producing 223 keys and 2067 values2015-10-27 06:49:26,435 INFO&nbsp; [Reflections] Reflections took 357 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:28,247 INFO&nbsp; [Reflections] Reflections took 554 ms to scan 239 urls, producing 67 keys and 398 values2015-10-27 06:49:28,563 INFO&nbsp; [Reflections] Reflections took 315 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:30,874 INFO&nbsp; [Reflections] Reflections took 783 ms to scan 239 urls, producing 25 keys and 45 values2015-10-27 06:49:31,297 INFO&nbsp; [Reflections] Reflections took 422 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:31,694 INFO&nbsp; [Reflections] Reflections took 195 ms to scan 239 urls, producing 16 keys and 35 values2015-10-27 06:49:32,022 INFO&nbsp; [Reflections] Reflections took 328 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:32,659 INFO&nbsp; [Reflections] Reflections took 208 ms to scan 239 urls, producing 7 keys and 9 values2015-10-27 06:49:32,920 INFO&nbsp; [Reflections] Reflections took 260 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:34,091 INFO&nbsp; [Reflections] Reflections took 1169 ms to scan 239 urls, producing 1595 keys and 7754 values2015-10-27 06:49:34,373 INFO&nbsp; [Reflections] Reflections took 280 ms to scan 1 urls, producing 882 keys and 3684 values2015-10-27 06:49:34,771 INFO&nbsp; [Reflections] Reflections took 220 ms to scan 239 urls, producing 67 keys and 322 values2015-10-27 06:49:35,067 INFO&nbsp; [Reflections] Reflections took 295 ms to scan 1 urls, producing 882 keys and 3684 values&nbsp;What is going on here and why so many attempts at locking, etc.???&nbsp;Is this the "problem"?&nbsp;Thanks.

tanyayatskovska · Answer

Hi Andyhore,
&nbsp;
&nbsp;
You can try improving the memory usage in Ready! API. Please refer to this article to learn how to do this: http://readyapi.smartbear.com/soapui/working/improving_memory_usage
&nbsp;
Does this help?

andyhore · Answer

&nbsp;Hi Tanya,&nbsp;Thanks for the reply. Unfortunately, this does not have any impact as that article effects running test suites within the product once it's open. My problem is startng ReadyAPI in the first place.&nbsp;Andy

tanyayatskovska · Answer

Thanks for your feedback, Andy.
In this case, I would suggest that you refer this issue to our Ready! API Support Team ( http://support.smartbear.com/product-list/ ) – they will need to investigate this.

Forum Discussion

Starting ReadyAPI 1.4.1 in our VM takes 5+ minutes...

4 Replies

Related Content

ReadyAPI Failed to start ReadyAPI

ReadyAPI 2.4 doesn't start

Getting java.lang.NoClassDefFoundError when starting ReadyAPI 2.0.2

ReadyAPI 3.3.2 - it doesn't close (waiting for 30 minutes now)

ReadyAPI and TestEngine with Zephyr Scale

Recent Discussions

How do I prevent a file path from being altered when being parsed by JsonSlurper in Groovy Script?

Multipart requests getting blocked by the Azure WAF 200003

Parameterising JDBC Connection Settings..Can you do it?

Darshan Hiranandani - How do I use an API in my application?

Mismatch between response from a CURL request and ReadyAPI response