# No response from RESTful WebService

**URL:** <https://forum.servoy.com/t/no-response-from-restful-webservice/16160>\
**Category:** Classic Servoy\
**Created:** [July 9, 2012, 2:28pm UTC](https://forum.servoy.com/t/no-response-from-restful-webservice/16160 "2012-07-09T14:28:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![GabrielWyss](https://avatars.discourse-cdn.com/v4/letter/g/ed8c4c/32.png) [@GabrielWyss](https://forum.servoy.com/u/GabrielWyss)\
**Post date:** [July 9, 2012, 2:28pm UTC](https://forum.servoy.com/t/no-response-from-restful-webservice/16160/1 "2012-07-09T14:28:06Z")

</div>

I defined a RESTful WebService. In the ws\_create method I process the received XML an create new records in different foundsets.  
In the calling application, I test with readyState() until the processing is finish.  
With smaller XML files, will mean not so much records to create all works fine. If the XML is bigger, all records will be created, but the calling application never receive the the state 4. There is allways the state 1.

Have any one a idea, why do I get this behavior?

Thanks for any help.

---

<div class="post-metadata">

**Author:** ![rgansevles](https://avatars.discourse-cdn.com/v4/letter/r/3d9bf3/32.png) [@rgansevles](https://forum.servoy.com/u/rgansevles)\
**Post date:** [July 30, 2012, 7:39am UTC](https://forum.servoy.com/t/no-response-from-restful-webservice/16160/2 "2012-07-30T07:39:18Z")

</div>

Gabriel,

What happens if you use your client code with another (non-Servoy) REST service?  
One that returns a lot of data.

Rob

---

<div class="post-metadata">

**Author:** ![GabrielWyss](https://avatars.discourse-cdn.com/v4/letter/g/ed8c4c/32.png) [@GabrielWyss](https://forum.servoy.com/u/GabrielWyss)\
**Post date:** [July 31, 2012, 5:31am UTC](https://forum.servoy.com/t/no-response-from-restful-webservice/16160/3 "2012-07-31T05:31:57Z")

</div>

Hello Rob

The client is a FoxPro client which use the Servoy REST client. I don’t have any other REST service to test this.  
But I find out that it is important to set the timeout (function setTimeouts) as the first step after initiate the Msxml2.ServerXMLHTTP object.  
At the moment, all works fine and I hope, it will stay that way.