"Darren Mombourquette" <darren@prairiefyre.com> wrote in message
news:411961a3.0406240423.163fcf7b@posting.google.com...
> Hi Byron,
> Thanks for responding, I get nothing in the event log. Is there a way
> to extend the timeout for the SoapReceiver?
>
> Darren
>
>
> "ByronKim" <byronkim@online.microsoft.com> wrote in message
news:<exlrsWbWEHA.2972@TK2MSFTNGP12.phx.gbl>...
> > Please check the event log and will see the detailed error, like
"'Failed to
> > dispatch".
> >
> > thanks
> > Byron KIM
> > "Darren Mombourquette" <darren@prairiefyre.com> wrote in message
> > news:411961a3.0406231318.196a8362@posting.google.com...
> > > I'm getting an Unhandled Exception from WSE2 and I know it's related
> > > to a timeout problem but I'm not sure where to set the timeout expiry.
> > >
> > > Essentially if you take the Sample project "Microsoft
> > > WSE\v2.0\Samples\CS\QuickStart\TcpStockSoapReceiver" in the
> > > StockServiceRequestReceiver.cs class and Sleep for over 2 minutes,
> > > before the response is sent back you will get a threadAbort exception.
> > >
> > > e.g. Add System.Threading.Thread.Sleep(new TimeSpan(0,2,15)); around
> > > line 80;
> > >
> > > The exception is as follows:
> > >
> > > Unhandled Exception: System.Exception: WSE104: An asynchronous
> > > callback raised a
> > > n exception. ---> System.Threading.ThreadAbortException: Thread was
> > > being aborte
> > > d.
> > > at
> >
Microsoft.Web.Services2.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope
> > > message)
> > > at
> >
Microsoft.Web.Services2.Messaging.SoapReceivers.OnReceiveComplete(IAsyncRe
> > > sult ar)
> > > at Microsoft.Web.Services2.AsyncResult.Complete(Boolean
> > > completedSynchronousl
> > > y, Exception exception)
> > > --- End of inner exception stack trace ---
> > > at
Microsoft.Web.Services2.AsyncResult.RaiseUnhandledException(Object
> > > o)
> > >
> > >
> > > Thanks,
> > > Darren Mombourquette

"Sidd" <ElCid@hotmail.com> wrote in message news:<40db6a2f$1@news.microsoft.com>...
> Hi Darren,
>
> There in total 4 timeout values that you need to watch for when
> designing your scenario:
> 1. Execution Timeout
> 2. Idle Timeout
> 3. Send Timeout
> 4. Receive Timeout
>
> What is most likely happening here is that on your server, since you are
> sleeping for a little over 2 minutes,
> your execution timeout at the server is being triggrered, hence you get
> the Thread Abort exception. Once the execution timeout
> is reached, the WSE framework will kill the thread that is currently
> processing the particular request, to provide some safeguard
> against someone who is continuously sending data for a very very long
> time.
>
> I actually inserted this line of code in the sample you mention, and
> after increasing the execution timeout at the server side, I was
> able to receive the request fine, without any exceptions happening.
>
> To change the execution timeout at the server, edit your config file and
> insert the following:
>
> <microsoft.web.services2>
> <messaging>
> <executionTimeout value="180" /> // denotes 180
> seconds
> </messaging>
> ...
> ...
> </microsoft.web.services2>
>
> You can find out how to set these individual timeouts by lookign at the
> WSE.Config file in the "Microsoft WSE\v2.0" directory
> of where you installed this.
>
> Hope this helps!
>
> Sidd
>
>
> "Darren Mombourquette" <darren@prairiefyre.com> wrote in message
> news:411961a3.0406240423.163fcf7b@posting.google.com...
> > Hi Byron,
> > Thanks for responding, I get nothing in the event log. Is there a way
> > to extend the timeout for the SoapReceiver?
> >
> > Darren
> >
> >
> > "ByronKim" <byronkim@online.microsoft.com> wrote in message
> news:<exlrsWbWEHA.2972@TK2MSFTNGP12.phx.gbl>...
> > > Please check the event log and will see the detailed error, like
> "'Failed to
> > > dispatch".
> > >
> > > thanks
> > > Byron KIM
> > > "Darren Mombourquette" <darren@prairiefyre.com> wrote in message
> > > news:411961a3.0406231318.196a8362@posting.google.com...
> > > > I'm getting an Unhandled Exception from WSE2 and I know it's related
> > > > to a timeout problem but I'm not sure where to set the timeout expiry.
> > > >
> > > > Essentially if you take the Sample project "Microsoft
> > > > WSE\v2.0\Samples\CS\QuickStart\TcpStockSoapReceiver" in the
> > > > StockServiceRequestReceiver.cs class and Sleep for over 2 minutes,
> > > > before the response is sent back you will get a threadAbort exception.
> > > >
> > > > e.g. Add System.Threading.Thread.Sleep(new TimeSpan(0,2,15)); around
> > > > line 80;
> > > >
> > > > The exception is as follows:
> > > >
> > > > Unhandled Exception: System.Exception: WSE104: An asynchronous
> > > > callback raised a
> > > > n exception. ---> System.Threading.ThreadAbortException: Thread was
> > > > being aborte
> > > > d.
> > > > at
> > >
> Microsoft.Web.Services2.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope
> > > > message)
> > > > at
> > >
> Microsoft.Web.Services2.Messaging.SoapReceivers.OnReceiveComplete(IAsyncRe
> > > > sult ar)
> > > > at Microsoft.Web.Services2.AsyncResult.Complete(Boolean
> > > > completedSynchronousl
> > > > y, Exception exception)
> > > > --- End of inner exception stack trace ---
> > > > at
> Microsoft.Web.Services2.AsyncResult.RaiseUnhandledException(Object
> > > > o)
> > > >
> > > >
> > > > Thanks,