Hi. Me again with an update. I've setted service.setTimeout(new Interger(1000 * 60 * 60) ) // one hour.
The webservice job is finished in about 40 minutes, but the client hangs up and times out in 1 hour (throwing an exception), and getting no response whatsoever. This is odd, because in previous tests with less time (11 minutes), i got the webservice to finish in less than 11 minutes, and the client got a response. Why setting such a big timeout, keeps the client hanged ? Is something here i'm missing ? Thanks. On Jan 18, 2008 12:10 AM, gaurav lall <[EMAIL PROTECTED]> wrote: > > > > > On Jan 17, 2008 4:06 PM, Noé Amorim <[EMAIL PROTECTED]> wrote: > > > > On Jan 17, 2008 11:59 PM, gaurav lall <[EMAIL PROTECTED]> wrote: > > > > > > > Will the client be able to read the response after the timeout ? > > > > > > Once the timeout occurs, there is normally an exception thrown/ > > > > > > Yes, right an exception is thrown, this means i have to catch the > > exception and send something back to the server, keeping it alive ? > > Just wild guessing, any example i can see or article to read, i'm kind > > a bit lost here. > I thought you mentioned that service does keep running on the server if > thats the case then you should not be sending anything back , can you try > setting the large timeout greater that normally what your service takes and > check . > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
