This is totally and utterly wrong :-) You should not have an RPC call that queries the DB and returns in 20 minutes or even 2 minutes...
If your calculations are that slow, make a process that precalculates and saves the results somewhere and then return this via the RPC call... On Mon, Nov 24, 2008 at 12:12 PM, ursprakash6 <[EMAIL PROTECTED]> wrote: > Hi All, > > How to change the default Client Timeout in BlazeDS -Remoteobject > AMFChannel? > > We are developing an Application in Flex, we are using the > Remoteobject concept to call backend method, > in that method we are doing some database related manipulation > operations,it will take 3 to 20 minutes approximately. > What happening here is remote calling is made successfully and the > operations are running perfectly in java side, > but the 5 th minute from the remoteobject call is made,the control is > returned to flex client[as fault event] and it executing the fault > event handler method, > though operation is not finished in backend side[its still running] > > how to override this 5 minute timeout to custom time (in my case its > ~50 minutes) > > Please help me out this Friends This is very urgent > > the mesage i'm getting in Faultevent > (mx.messaging.messages::ErrorMessage)#0 > body = (Object)#1 > clientId = (null) > correlationId = "D7300EA9-2865-17DF-7157-B411C50C1276" > destination = "" > extendedData = (null) > faultCode = "Channel.Call.Failed" > faultDetail = "NetConnection.Call.Failed: HTTP: Failed" > faultString = "error" > headers = (Object)#2 > messageId = "5D758FD4-5072-F686-0DF3-B41662EF7CD0" > rootCause = (Object)#3 > code = "NetConnection.Call.Failed" > description = "HTTP: Failed" > details = "https://192.###.###.###:444/samplapp/messagebroker/amf"; > level = "error" > timestamp = 0 > timeToLive = 0 > > we are using mx.messaging.channels.AMFChannel & > mx.messaging.channels.SecureAMFChannel in service config > > Thanks In Advance > > GnanaPrakasam T. > > > -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation [EMAIL PROTECTED],
