Hi Jerome, Awesome and thanks, the 2.1 snapshot indeed works !
A small newbie question: My client implementation directly gets the JsonRepresentation from server and I am not explicitly using any streams. I think, restlet internally transfers it through streams only, but is using stream to transfer large JsonRepresentation a better idea ? Regards Lokendra On Mon, May 16, 2011 at 11:44 PM, Jerome Louvel <[email protected]>wrote: > Hi Lokendra, > > > > Version 2.0.7 and 2.1 M4 introduced a regression that could cause blocking > for large entities. This is fixed in the latest 2.1 snapshot though. > > > > Another workaround is to use another HTTP connector such as > org.restlet.ext.simple.jar or org.restlet.ext.jetty.jar > > > > Best regards, > Jerome > -- > Restlet ~ Founder and Technical Lead ~ > http://www.restlet.org<http://www.restlet.org/> > Noelios Technologies ~ http://www.noelios.com > > > > > > > > *De :* Lokendra Singh [mailto:[email protected]] > *Envoyé :* lundi 16 mai 2011 20:10 > *À :* [email protected] > *Objet :* Returning large JSON Representation causes client to time-out > (Internal Connector Error-1002) > > > > Hi, > > > > My server contains a @Post method which receives some params and returns a > JsonRepresentation to the client. The client retrieves the Json Object from > JsonRepr. by getJsonObject() method. > > Returning a large JsonRepresentation causes client thread to time out : > 'Internal Connector Error (1002) - The calling thread timed out while > waiting for a response to unblock it'. > > Please su > > > > > Regards > Lokendra > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2738296
