This is a migrated thread and some comments may be shown as answers.

Command Timeout for SP in Open Access Classic

1 Answer 97 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
devoas
Top achievements
Rank 1
devoas asked on 25 Nov 2015, 01:32 PM

Hi,

 We are using Open Access Classic and having problem that Long running Store procedure throwing Request timeout  messages....In app.config we already set conTimeout = 720 but still after 2 mins it thru Request Timeout Message....

We are using it in our aps.net projects...  and have following setting in app.config 

    <backendconfigurations>
      <backendconfiguration id="mssqlConfiguration" backend="mssql">
        <mappingname>mssqlMapping</mappingname>
        <logging.logEvents>none</logging.logEvents>
        <conTimeout>720</conTimeout>
        <maxActive>100</maxActive>
        <maxIdle>100</maxIdle>
        <lockTimeout>20000</lockTimeout>
      </backendconfiguration>

And while setting Object scope we have following Code: 

        string myconfig =
                 "<openaccess>" +
                 "<references>" +
                 "<reference assemblyname='" + AssemblyName.Trim() + "' />" +
                 "</references>" +
                 "<connections>" +
                     "<connection id='" + ConnectionID + "'>" +
                        "<databasename>" + Database + "</databasename>" +
                        "<servername>" + server + "</servername>" +
                        "<integratedSecurity>false</integratedSecurity>" +
                        "<user>" + UserID + "</user>" +
                        "<password>" + password + "</password>" +
                          "<backendconfigurationname>mssqlConfiguration</backendconfigurationname>" +
                    "</connection>" +
                "</connections>" +
                "</openaccess>";
            XmlDocument xmlDoc = new XmlDocument();
            xmlDoc.LoadXml(myconfig);

            XmlDocument xmlDoc = new XmlDocument();
            xmlDoc.LoadXml(myconfig);

            return Telerik.OpenAccess.Database.Get(ConnectionID, xmlDoc.DocumentElement).GetObjectScope();

 

Can you pls advise what is missing in this code.

 

Thanks 

devoas.

 

 

 

1 Answer, 1 is accepted

Sort by
0
Thomas
Telerik team
answered on 27 Nov 2015, 03:01 PM
To me, the configuration looks correct and you should be able to perform long running SQL when the server does not require locks to be held longer than 20seconds. Please check that this is not causing 
the issue - even though 20 seconds is quite a long time for a database server to hold a lock.
In addition you should set the testInterval to 720 too; that would mean we do not wake up so often to check for busy connections.

Regards,
Thomas
Telerik
 
Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.
Tags
General Discussions
Asked by
devoas
Top achievements
Rank 1
Answers by
Thomas
Telerik team
Share this question
or