Forum Discussion

amit07's avatar
amit07
New Contributor
7 years ago

Rest call still running, server already responded response

Hi There, I am running a rest request (GET  http://<IP>:8080/app1?queryParam=1000 ) on SoapUI 5.4.0 (community edition) Case-1: When server responding within 5 mintes with statusCode =200,, =>the...
amit07's avatar
amit07
New Contributor
7 years ago

Hi Nmrao,

 

Server is taking sometime 70 -80 minutes to complete, So for saver side I configured SocketTimeout accordingly.

This service is synchronous.

In my case Soapui is accepting response returned by server only when service is completing in 5 minutes, otherwise soapui doesn't accepting server response which is completed after 10 minutes.

 

Is there any configuration for fetch response call-back till xxxx milisecond, after which it is not soapui doesn't looking for response call-back of the request?

 

Please reply ....

 

-Amit

nmrao's avatar
nmrao
Icon for Champion Level 2 rankChampion Level 2
7 years ago
I am not sure which end user accepts this behaviour or waits for so much of time to receive a response.

If that is going to take such a long time, why can't it be an asynchronous?
  • amit07's avatar
    amit07
    New Contributor
    7 years ago

    Q.       If that is going to take such a long time, why can't it be an asynchronous?

    Ans.   I cann't change exposed service from sync to async. I have to just test the service....

     

    In service side rquest completed after in 7 minutes.... where In soapui HTTP log the http-connection still opened even after 15 miute.....

    • nmrao's avatar
      nmrao
      Icon for Champion Level 2 rankChampion Level 2
      7 years ago
      May be because of the soapui settings you made to wait for the long. But any ways, that might not be helpful if service is going to take unknown time to respond.