Re : Timeout in long running timer-action

Post Closed

Matthias Preuter

MVP

Solved

Re : Timeout in long running timer-action

Question

After 2 minutes, a long running timer-action is timed out, i now it is a setting in the .Net 2.0 configuration. Can anyone tell where to set it.
Regards,
Matthias

17 Apr 2008

Matthias Preuter

MVP

Solution

Found it, in .Net 2.0 you have to set the Timeout in the Machine.config:

in the section <system.web> the line <httpRuntime maxRequestLength="65536" executionTimeout="300" /> must be added.

See solution in context

21 Apr 2008

Pedro Gonçalves

Staff

Hi Matthias,

Take a look at Miguel João's 4th post in https://www.outsystems.com/NetworkForums/ViewTopic.aspx?TopicId=3486

Hope that helps.
Regards,

Pedro

17 Apr 2008

AcacioPN

Staff

Hello Matthias

If you are talking about the OutSystems timers, their timeout is not controlled by any .NET 2.0 setting, but instead by the timeout setting that is defined for that timer. In Service Studio, you can change this setting when creating the timer; in Service Center, you can change this setting by accessing Factory | eSpaces, choosing your eSpace and clicking the Timers tab.

We find it strange that you mention 2 minutes, since the default timeout is of 20 minutes. Is this a typo or are your timers really aborting after 2 minutes?

Cheers,

17 Apr 2008

1 reply

21 Apr 2008

Show thread

Hide thread

Matthias Preuter

MVP

Solution

Found it, in .Net 2.0 you have to set the Timeout in the Machine.config:

in the section <system.web> the line <httpRuntime maxRequestLength="65536" executionTimeout="300" /> must be added.

21 Apr 2008

Jeroen Vormer

Hi Matthias,

did this solve your issue?

Best regards,
Jeroen

14 Sep 2020

Hans Dollen

Jeroen,

you're replying on a post of more than 12 years old :). If you have a question I would suggest to create a new Post.

Regards,

Hans

14 Sep 2020

Jeroen Vormer

Solved by editing the application pool recycling settings.

17 Sep 2020