Hello John,
I have created a simple example based on your scenario that includes a “WebDataGrid” with 15 000 rows and paging enabled with 100 records per page.
I have handled the “PageIndexChanged()” event and put thread in “Sleep” mode for 30 sec.:
protected void WebDataGrid1_PageIndexChanged(object sender, Infragistics.Web.UI.GridControls.PagingEventArgs e)
{
Thread.Sleep(30000);
}
When the thread resumed its execution after “Sleep” mode the error message from the page was sent – "Server does not respond.".
Then I have added the following function (provided in previous responses) to the “Grid_Initialize()” client-side event:
function WebDataGrid1_Grid_Initialize(sender, eventArgs)
{
///<summary>
///
///</summary>
///<param name="sender" type="Infragistics.Web.UI.ControlMain"></param>
///<param name="eventArgs" type="Infragistics.Web.UI.EventArgs"></param>
$find("<%= WebDataGrid1.ClientID%>")._callbackManager.setTimeout(31000);
}
The error was not present anymore and after 30 sec. of waiting the paging displayed the next page from the grid without the above error message.
You can try the above resolution and let me know what the results are on your machine.