If the batch process is going to run for 5 hours, might it be better to use an a-synchronous, versus synchronous, approach to the problem? Jack
-----Original Message----- From: Scott Nichol [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 9:19 AM To: [EMAIL PROTECTED] Subject: Re: Client call timeout I do not think I understand the scenario you describe. What network connection are you talking about? If it is the connection over which the SOAP call is being made, I don't understand the stuff about re- connecting. There is no code in the Apache SOAP HTTP transport that would cause such a reconnect to happen. If the connection is broken, the read from the socket on which the client code blocks would throw an exception. Could you give more details? On 4 Apr 2003 at 21:01, Alan Ong wrote: > In my java code: > > Call oCall = new Call(); > > oResponse = oCall.invoke(url); > > These rpcs usually last for 5 or more hours because it is doing some batch > processing. > But if the network connection is broken in the middle of the invocation, but the > call will not return an exception, instead it will wait for the connection to > return. If the connection returns, it will continue where it left off. Is there a > way to tell if the connection is lost so that an error message can be displayed to the user. These is needed because if the connection will not return, then the caller will wait forever, thus hang the program. > > Can anybody help me out. > > Thanks for your time. > > "Two heads are more than one" -- Cat Dog > > "To pee is to relieve" -- Anonymous > > Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
