"Cedric" wrote:

> Hi all,
>
> We have some performance issues on a .NET 2.0 app. However we cannot modify
> it, we don't have the sources.
> Reading the logs, the error is a timeout happening in some Web Service call.
>
> With the sources, it would be easy (?!), would have just changed
> WebRequest.Timout to a bigger value, but we don't have sources.
>
> Is there a way to change the default value, which is 100 seconds,
> declaratively (in web.config, machine.config... etc.) or even somewhere else
> like in the registry? Or is it hard coded in the framework?
>
> I have been struggling on this, but haven't found a lead...
>
> Thanks,
>
> Cédric
>
>

"Jakob Christensen" <JakobChristen***@discussions.microsoft.com> wrote in
message news:47C26E7B-83AF-4D84-80E0-0AA6A850D2D8@microsoft.com...
> You can set executionTimeout for the HttpRuntime element in web.config:
> http://msdn2.microsoft.com/en-us/library/e1f13641.aspx
>
> HTH, Jakob.
> --
> http://www.dotninjas.dk
>
>
>
> "Cedric" wrote:
>
>> Hi all,
>>
>> We have some performance issues on a .NET 2.0 app. However we cannot
>> modify
>> it, we don't have the sources.
>> Reading the logs, the error is a timeout happening in some Web Service
>> call.
>>
>> With the sources, it would be easy (?!), would have just changed
>> WebRequest.Timout to a bigger value, but we don't have sources.
>>
>> Is there a way to change the default value, which is 100 seconds,
>> declaratively (in web.config, machine.config... etc.) or even somewhere
>> else
>> like in the registry? Or is it hard coded in the framework?
>>
>> I have been struggling on this, but haven't found a lead...
>>
>> Thanks,
>>
>> Cédric
>>
>>

"Cedric" wrote:

> Hi Jakob,
>
> Thanks a lot for your answer.
> exectutionTimeout will set the time the web server allows for a task to
> execute (processed by the w3wp.exe process potentially).
> The timeout I would like to set is on the client side. The client calls the
> web service and as the answer from the server is too long to come, it comes
> to the timeout. This timeout is handled through the WebRequest.Timout or
> HttpWebClientProtocol.Timeout.
>
> So it would be this property's default value that I would need to set
> without modifying the code...
>
> Any idea?
>
> Thanks,
>
> Cédric
>
>
> "Jakob Christensen" <JakobChristen***@discussions.microsoft.com> wrote in
> message news:47C26E7B-83AF-4D84-80E0-0AA6A850D2D8@microsoft.com...
> > You can set executionTimeout for the HttpRuntime element in web.config:
> > http://msdn2.microsoft.com/en-us/library/e1f13641.aspx
> >
> > HTH, Jakob.
> > --
> > http://www.dotninjas.dk
> >
> >
> >
> > "Cedric" wrote:
> >
> >> Hi all,
> >>
> >> We have some performance issues on a .NET 2.0 app. However we cannot
> >> modify
> >> it, we don't have the sources.
> >> Reading the logs, the error is a timeout happening in some Web Service
> >> call.
> >>
> >> With the sources, it would be easy (?!), would have just changed
> >> WebRequest.Timout to a bigger value, but we don't have sources.
> >>
> >> Is there a way to change the default value, which is 100 seconds,
> >> declaratively (in web.config, machine.config... etc.) or even somewhere
> >> else
> >> like in the registry? Or is it hard coded in the framework?
> >>
> >> I have been struggling on this, but haven't found a lead...
> >>
> >> Thanks,
> >>
> >> Cédric
> >>
> >>
>
>