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
> Hi Byron,
> Thanks for responding, I get nothing in the event log. Is there a way
[quoted text clipped - 26 lines]
> > > 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
Darren Mombourquette - 25 Jun 2004 15:36 GMT
Excellent Sidd,
Thank you.
Darren
> Hi Darren,
>
[quoted text clipped - 88 lines]
> > > > Thanks,
> > > > Darren Mombourquette