WSE setting "executionTimeout"

Tech-Archive recommends: Fix windows errors by optimizing your registry

In the web.config file the WSE setting "executionTimeout" does not seem to
have any affect. [I tried two different ways to set this. See below].
Is this used at all? Am I missing something? Is the httpRumTime
"executionTimeout" take precedence over it?

Any help is greatly appreciated.

<microsoft.web.services2>
<messaging>
<maxRequestLength>51200</maxRequestLength>
<executionTimeout value="10" />
<!--
<transports>
<add scheme="soap.tcp">
<executionTimeout value="10" />
</add>
</transports>
-->
</messaging>
</microsoft.web.services2>



Thanks,
Ajay Choudhary



.

Relevant Pages

  • WSE setting "executionTimeout"
    ... Am I missing something? ... Is the httpRumTime ... "executionTimeout" take precedence over it? ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Operator precedence: am I missing something?
    ... Or am I missing something obvious? ... The precedence table does not convey all information that the ... Open one of your C books and see whether the cast ... if you are looking for a good C reference that's what C reference ...
    (comp.std.c)
  • Re: find/grep file extensions
    ... > If you have GNU find, ... You need parenthesis as -a (implied when missing) has higher ... precedence than -o ...
    (comp.unix.questions)
  • Re: Newbie question: it works, but whats it doing?
    ... > Am I missing something? ... Addition works the same no matter how you ... > paranthesise the statement ...
    (alt.comp.lang.learn.c-cpp)