Ajax Timeout

[Dominik]

Hi,

We have a long server side process that can easily produce an ajax timeout.

We have changed our request timeout, suposed to be infinite, more or less in this way:

<Proxy>
   <ext:HttpProxy Url='<%# this.Page.GetRouteUrl(this.Area, new { controller="Customers", action="Index" }) %>'
        Method="GET" AutoDataBind="true" Timeout="2147483647" />
</Proxy>

With this timeout the full process is completed, no matter how many time it takes. But when it exceeds from 30 seconds, this error thows in the middle of the process:

Request Failure

Status Code: -1
Status Text: transaction aborted


How could we avoid this timeout error? How could we define an ajax timeout only for this request?

Thanks in advance,

Dominik.

[Dominik]

Hi agian,

Please any advice about how to solve this problem?

Thanks,

Dominik.

[geoffrey.mcgill]

Hi,

The ASP.NET runtime might be timing out. I believe there is a setting in the Web.config to override.

Hope this helps.

[Dominik]

Well,

If I set this configuration, it still fails:

<httpRuntime executionTimeout="36000" />

Is there any other Ext.NET configurable parameter?

Thanks.

[Dominik]

Hi all again,

Finally I got it!

We were sending an store reload request, but when our windows is hiden we are perfroming also a Release call in this way:

        <DirectEvents>
            <Hide Url='<%# this.Page.GetRouteUrl("Default", new { controller="Filtros", action="Release" }) %>' 
                    AutoDataBind="true">
                <ExtraParams>
                    <ext:Parameter Name="TipoFiltro" Value="tfDepuracionDatos" Mode="Value" />
                </ExtraParams>
            </Hide>
        </DirectEvents>

I don't know exaclty why, but despite both requests were sent at the same time, they are being executed syncronously. I imagine it is a Session problem...

Any way, I added another Timeout to the DirectEvent to avoid this problem.

Regrads,

JA Reyes.