Hi,
If we are definitely talking about the same delay i.e. the 5 seconds it takes SoapUI to initialise itself when you make the first request to the mock, then I think it is just a case of 'warming it up' or initialising it first. Taking a look inside the generated mock war file, I think all that needs to happen is to initialise the MockAsWarServlet so that it loads automatically after the war is deployed in tomcat. To do this, please try adding the following line to WEB-INF/web.xml
<servlet>
<description></description>
<display-name>SoapUIMockServlet</display-name>
<servlet-name>SoapUIMockServlet</servlet-name>
<servlet-class>com.eviware.soapui.mockaswar.MockAsWarServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<init-param>
After I did this, I can see the same SoapUI core initialization logs that I posted in the previous reply and the mock then seems to respond instantly without delay or need for 'warm-up'.
Thanks,
Rup
Rupert,
Looks like you might have the solution for a WAR file. As I mentioned in the first post, I'm running from Maven using the SOAPUI plugin. There maybe a similar issue with the plugin vs the WAR. But how to configure the SOAPUI maven plugin to do the same as you have suggested in your last post?
I am going to try to start the mock service via a "load script" in the project file to see if that gets the mock started when the project is loaded, rather than when the first message is received. I'm not sure, but potentially the SOAPUI maven plugin starts the mock service anyway?
I'll let you know how I get on and if you can help with the setup of the maven plugin to get the same behaviour as the WAR that would be much appreciated.
Many thanks
Ed
