Thanks Jonathon, I'll get the guys to do that - much appreciated.
On Wed, Mar 18, 2009 at 7:17 PM, Jonathon Stierman <[email protected]>wrote: > You could be hitting your servers’ (IIS, Apache) maximum number of > connections – which means your application (and thus your custom logs) > wouldn’t even be run. The server would just eat the requests and send back > a 500 level HTTP response. > > > > Check your servers’ error logs, and see if anything appears in there. > > > > Jonathon > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *nwebb > *Sent:* Wednesday, March 18, 2009 1:32 PM > *To:* [email protected] > *Subject:* [flexcoders] What are the chances Flex could be causing this? > > > > Hi, we've got a webservice with about 10 methods. When the application > starts up it calls about 6 of them in quick succession (I'm currently > chaining those calls). > > > If I upload the SWF to our dev environment, create a tab-group in IE (10 > tabs in total), with each tab loading the swf, I can load 10 instances of > the application similtaneously. > When I do that I'm seeing that several instances of the app are throwing > errors like this: > > 18:06:08.273 | [ERROR] | mx.messaging.Producer | > 'B8ED2C1F-ABBE-DB29-3DB4-1AC289775CF2' producer fault for > 'F87115A3-7C5D-2F13-2EA0-1AC2ED13E733'.18:06:08.304 | [ERROR] | > Tools.business.AbstractRPCConsumer.fault | faultCode:Server.Error.Request > faultString:'HTTP request error' faultDetail:'Error: [IOErrorEvent > type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error > #2032: Stream Error. URL: http://dev- ........ > > I'm pretty sure this is a server-side issue but want to make absolutely > sure. The server logs in place don't show any errors (but I'm just a > front-end guy looking at some custom error logs - I could easily be missing > something!) - many of the Flex calls are getting rejected. > > Or could this be a red herring? Perhaps the browser is imposing a limits on > the number of connections opened and I can't test things this way. If > anyone has thoughts on whether I could be doing anything weird on the > front-end to cause this please let me know. > > Thanks. > > >
