Tuesday, January 26, 2010

FaultEvent.FAULT night-mare when network b/w is low / load is high on the server

I have a task ahead tomorrow to resolve why the flex code randomly hits FaultEvent.fault event handler when the network bandwidth is low and the load on the coldfusion server is high. Watching the HTTP requests through Fiddler (HTTP Debugger) confirms that the request and response packets go through fine without any soap faults / http errors. So the big question ahead is why does some users encounter fault events randomly instead of hitting the ResultEvent.RESULT when the response looks fine on the network http debugger?

Herez a glimpse of what we have -

- We have a CF coldspring implementation exposing webservice operations.
- Flex app loads the wsdl's on load

As the user logs in, we invoke operations on the webservices -

Our end users are running 0.45 Mbps upload and download speeds... Has anyone encountered something like this before? Whats going wrong is a big question for me.... WS code is just a wrapper on the bottom line HTTPService in as. Guess I get a chance to reproduce the scenario and i get to debug through the flex framework to see which piece is actually getting me into this..

2 comments:

Joeflash said...

I'm on a wireless internet connection at home, cause I live rurally, and during peak network times my connection drops down as low as 0.20 Mbps (I know it sucks!!) - when that happens I get Fault Errors on media players and server-connected apps when I'm surfing. If I wait, and go back to the site, it's fine.

Keep in mind that when Speedtest.net tells me my connection speed is 0.20Mbps, it's an average. I look at my actual bandwidth with a realtime monitor (http://www.bwmonitor.com) it's all spiky, cutting in and out like crazy, like burst traffic. So I suspect Fault Errors under those conditions have something to do with micro-sized network timeouts, if there is such a thing.

Hope that helps.

Marti said...

Hey, I've noticed similar problems while uploading some stuff. I didn't find a fix for that except ignoring the event
http://blog.formatlos.de/2008/11/13/filereference-upload-ii/