I wonder if it's the actual size or whether there is something in the data that it doesn't like. Could you try a different portion of the data (Say between the 60K point and 120K ?).
--- In [email protected], "michaelisraelcaplan" <mcap...@...> wrote: > > Ah, MaxReceivedMessageSize is not a Windows limit,per se, but a Windows WCF > limit that is programatically controlled by the SOAP server. That shouldn't > be a factor with the "out of bounds" fault? > > > --- In [email protected], "michaelisraelcaplan" <mcaplan@> wrote: > > > > Interesting point. I tried truncating my byte array down to 60KB, I still > > got the "out of bounds" fault. However, if i drop the byte array down to > > 10KB, no "out of bounds" error. > > > > Somewhere between the two (60KB and 10KB) is the breaking point. I've read > > through the article you referenced (thanks for the link!), but still don't > > see what quota parameter Flex would be blowing. Are we talking > > MaxReceivedMessageSize? > > > > > > The other interesting thing is that I'm seeing much greater volume than > > 60KB being transmitted to the SOAP server when inspecting incoming data > > server side using Wireshark. If this is a quota violation being triggered, > > how would it enforce on the packet data? Would some of it be dropped? > > Maybe everything following the violation? > > > > Thanks, > > > > Mike > > > > > > --- In [email protected], "valdhor" <valdhorlists@> wrote: > > > > > > I wonder if you have hit a windows limitation. This article may give you > > > some ideas... > > > > > > http://blogs.msdn.com/drnick/archive/2006/03/10/547568.aspx > > > > > > > > > --- In [email protected], "michaelisraelcaplan" <mcaplan@> wrote: > > > > > > > > I've been looking at this problem for just about a day straight now, > > > > and just can't see why I'm getting an out of bounds error on send. > > > > I've tried updated to the latest Gumbo nightly (9377), which no luck. > > > > > > > > My code to launch the WebService call looks like this: > > > > > > > > > > > > _calibrationData = new ByteArray(); > > > > var stream:FileStream = new FileStream(); > > > > stream.open(file, FileMode.READ); > > > > stream.readBytes(_calibrationData, 0, stream.bytesAvailable); > > > > > > > > var token:AsyncToken = this._service.mLoadCalibration(file.name, > > > > _calibrationData); > > > > token.addResponder(this._mLoadCalibrationResponder); > > > > > > > > > > > > Which seems to be a-okay. Or, am I missing something obvious? > > > > > > > > > > > > I'm pretty sure I've hit up against a SDK bug. I've opened a bug report > > > > with Adobe, to track this issue at > > > > http://bugs.adobe.com/jira/browse/SDK-22751 > > > > > > > > > > > > Anyone else transferring "large" (1MB) base64 encoded data using the > > > > Flex webservice client? > > > > > > > > > > > > Any feedback highly welcome! > > > > > > > > Thanks, > > > > > > > > Mike > > > > > > > > > >
