• Replies 17 replies
  • Subscribers 337 subscribers
  • Views 155 views
  • Users 0 members are here
Related

Web API timeout

Former Member
Former Member $organization

We are running some custom procedures though the Web API. Some of them run for more than 30 seconds, so we are getting the following error:

"System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding."

We have increased all the timeouts settings we found in web.config and in t_defaults without success. Any ideas of what timeout could be the one triggering this error?

Thanks

 

  • Former Member
    Former Member $organization

    Kind of related to this topic.

     

    Does anyone know if  there is a list of tables that can safely be purged without affecting Tess’ functions?

     

    Fernando Margueirat
    Business Analyst
    The National Ballet of Canada
    470 Queens Quay West
    Toronto, Ontario
    M5V 3K4
    P: 416 345 9686 x453
    F: 416 345 8323

     

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Patrick FitzGerald
    Sent: October-24-14 11:08 AM
    To: Fernando Margueirat
    Subject: Re: [Tessitura Technical Forum] Web API timeout

     

    Does anyone know the recommend number of rows that should be in T_WEB_SESSION_SESSION? It looks like earlier in the thread Simon is recommending 5,000,000 rows. 

    For various reasons, I would like to keep 3 years of data, which well exceeds that number in our session table.  I guess I am wondering where that 5,000,000 number came from, if it is one that has been tested and validated or just a best guess.

    Any advice on this would be appreciated.


    Thanks,
    Patrick 

    From: Sujit Nair <bounce-sujitnair1979@tessituranetwork.com>
    Sent: 10/21/2014 7:00:47 PM

    Thanks for your response Gawain.

    Yes we did try to clear a huge chunk before, and I think the UP_CLEAR_WEB_TABLES procedure doesn't cope very well with that. You're right, doing the deletion in small chunks is the way to go looks like, would be a slow process though to get through around 4 years worth of data :)

    Cheers,

    Sujit.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • $organization in reply to Sujit Nair

    Hi Sujit,

    I am so embarrassed, I posted this and then I did not subscribe to the replies. If you are still interested, we can share the scripts with you. We did this on our own, and yes, reducing the size of the database was our motivation. I do not remember the exact numbers, but the size of the compressed back ups was reduced considerably. I will make sure I subscribe to this discussion this time.