[Reg] schema load affects first request SLA
Hello. I am using SoapUI Pro 4.6.4 and have some testsuites running through "SoapUI Pro 4.6.2 Maven2 TestCase Runner". (This reproduces with the 4.6.4 plugin.) I noticed that the Response SLA fo...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi,
Thanks for the project file. We have managed to reproduce the behavior of the first request being slower, although the delay is smaller than what you seem to be experiencing. We get a delay of about 60 ms for the first request.
From what we can see when trying to figure out the root cause is not the loading of the schema, but rather some internal HttpClient code. A workaround you could try is to add a dummy HTTP Test Request as the first step of your test case just to circumvent extra time being added to the first real request.
We have a logged an issue (SOAP-1576) in our internal bug tracking system for figuring out what is actually causing this and fixing this. Thank you for reporting this issue.
Regards
Joel Jonsson
SmartBear Sweden
Thanks for the project file. We have managed to reproduce the behavior of the first request being slower, although the delay is smaller than what you seem to be experiencing. We get a delay of about 60 ms for the first request.
From what we can see when trying to figure out the root cause is not the loading of the schema, but rather some internal HttpClient code. A workaround you could try is to add a dummy HTTP Test Request as the first step of your test case just to circumvent extra time being added to the first real request.
We have a logged an issue (SOAP-1576) in our internal bug tracking system for figuring out what is actually causing this and fixing this. Thank you for reporting this issue.
Regards
Joel Jonsson
SmartBear Sweden