In that cases it could be a server side error, some DB connection timeout or
other error which might not have been  handled in a try catch block( in case
you are handling exceptions through a pre-defined schema)

Thats all I can add.

~Peeyush


On Mon, Apr 21, 2008 at 1:13 PM, Gupta, Pradeep <[EMAIL PROTECTED]>
wrote:

>    I am tracing the SOAP message and it is fine. The error is happening
> sporadically i.e. if I issue multiple request to the server 10/15 calls
> succeed however fails randomly while getting the response.
>
>
>
> Any idea?
>
>
>
> Thanks
>
> Pradeep
>
>
>
>
>
>
>  ------------------------------
>
> *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Peeyush Tuli
> *Sent:* Monday, April 21, 2008 11:03 AM
>
> *To:* flexcoders@yahoogroups.com
> *Subject:* Re: [flexcoders] Getting Error #2032: Stream Error randomly in
> Flex3.0
>
>
>
> There can be issue with parsing the SOAP message server-side or client
> side.
> Please use an HTTP Proxy like Charles to check the request - response
> message
> in detail.
> It will report you the correct error message.
>
> ~Peeyush
>
> On Mon, Apr 21, 2008 at 10:58 AM, Gupta, Pradeep <[EMAIL PROTECTED]>
> wrote:
>
> Thanks for your response.
>
>
>
>
>
> It doesn't seem to be the server side problem. I have tested this by
> hosting web service locally. It is .NET based service.
>
>
>
> Do you still think it is the server side problem?
>
>
>
> Thanks
>
> Pradeep
>
>
>  ------------------------------
>
> *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Josh McDonald
> *Sent:* Monday, April 21, 2008 10:56 AM
> *To:* flexcoders@yahoogroups.com
> *Subject:* Re: [flexcoders] Getting Error #2032: Stream Error randomly in
> Flex3.0
>
>
>
> It could be a server-side problem, what's your back-end?
>
> On Mon, Apr 21, 2008 at 3:22 PM, Gupta, Pradeep <[EMAIL PROTECTED]>
> wrote:
>
> Hi,
>
> I am getting a Stream Error #2032: in Flex 3.0 randomly while calling a
> web service. The web service is returning the data correctly, but some
> how the fault handler gets executed though randomly.
>
> Does any one have any idea on this problem?
>
> I appreciate your help on this
>
> Thanks
> Pradeep
>
>
>
>
> --
> "Therefore, send not to know For whom the bell tolls. It tolls for thee."
>
> :: Josh 'G-Funk' McDonald
> :: 0437 221 380 :: [EMAIL PROTECTED]
>
>
>
>  
>

Reply via email to