On Sat, Apr 24, 2010 at 1:20 AM, Betts, Hendry <[email protected]>wrote:
> First, I think (and I hope others would agree) that it is a bad idea to > use an “infinite” timeout on a web service. Any service that is taking > “forever” to respond is broken (IMO). > The problem here is that the server takes a lot of time to process the message and that processing time is not predictable at the deployment time. One option is to use dual channel. i.e. use the useSperateListner to true. And make the server side asynchronous as well. But inorder to do this client should be in a visible ip for server. thanks, Amila. > > > If you make your service client’s timeout infinite, how do you know when it > failed? Also, you would have to write in a number of handlers that deal > with the various timeout scenarios rather than relying on the http client’s > native timeout functionality. > > > > Ultimately, your timeout is managed in two places – at the web service’s > web server and at the web service client’s timeout value. Perhaps you > should look at making your service a little more “chatty” and allowing it to > send/receive smaller data packets to avoid becoming a hung process. > > > > > ------------------------------ > > *From:* rahul yadav [mailto:[email protected]] > *Sent:* Tuesday, April 20, 2010 6:33 AM > *To:* [email protected] > *Subject:* infinite timeout for WS request > > > > is there a way to set infinite time in.. > *org.apache.axis2.client.Option. > setTimeOutInMilliSeconds(long timeOutInMilliSeconds).* > > > by default it timeout after 2000 milliSeconds, we want it to keep waiting > for infinite time.I am using Axis1.5.1 > > Thanks & Regards, > Rahul Yadav > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
