locked
connection time out error RRS feed

  • Question

  • hi

    we are getting connection time out in our application for 2-3times intially when we use,after this the application is working fine for whole day.this is getting repeated for  everyday.

    application is hitting our test db server,no of users are also very less

    my observations

    ->i can't see any time out error in log

    ->no blockings

    ->remote login timeouts &remote query timeout run value are set to 1000

    ->in application connection time out is set to zero

    ->cpu and memory utilization are also normal

    server is on SQL 2012

    could some one help me on this to overcome the initial time out error in application and the things which need to be modified or monitored from DB end

    Tuesday, October 7, 2014 6:25 AM

All replies

  • Hi,

    The following blog may help you to solve your problem.

    Timeout expired


    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    Praveen Dsa | MCITP - Database Administrator 2008 | My Blog | My Page

    Tuesday, October 7, 2014 6:40 AM
  • ->in application connection time out is set to zero

    Are you sure? There are two different can timeouts you can experience: connection timeouts and command timeouts. The link posted by Praveen is about command timeouts. The default for the connection timeout is 15 seconds and the command timeout is 30 seconds. It is very reasonable to set the command timeout to 0, which means that wait forever. Waiting forever is less reasonable for the connection timeout. But when I think of it, I am not sure that 0 means "forever" for the connection timeout. So if you have set it to zero, maybe that is your problem.

    Else, I would suspect a network problem.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Tuesday, October 7, 2014 7:48 AM
  • hi

    connection time out is set to zero and command time out is set to 240

    is there anything else that we can do

    Tuesday, October 7, 2014 9:23 AM
  • hi

    connection time out is set to zero and command time out is set to 240

    is there anything else that we can do

    try to set command time out to 0 as well, if this works properly then you can change this setting later on.

    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    Praveen Dsa | MCITP - Database Administrator 2008 | My Blog | My Page

    Tuesday, October 7, 2014 9:25 AM
  • i have tried that already,but it didn't work
    Tuesday, October 7, 2014 10:42 AM
  • connection time out is set to zero and command time out is set to 240

    I would recommend that you set the connection timeout to 60 to see what happens.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Tuesday, October 7, 2014 11:03 AM
  • which application use are using if are using .net application then specify the connection pooling details

    try yo enable TCP/IP chimney  this is may be helpful to you.


    Thanks

    Tuesday, October 7, 2014 11:25 AM
  • First step: did you see if your SQL instance is started in services.msc?
    Tuesday, October 7, 2014 11:54 AM
  • services are running fine
    Wednesday, October 8, 2014 6:14 AM
  • Did you try Ping command to the server with -t? Try to find any error message.
    Wednesday, October 8, 2014 6:22 AM
  • i have pinged the server and there is no packet loss and time is less than 1ms
    Wednesday, October 8, 2014 6:50 AM
  • Did you try setting the connection timeout to 60 yet?


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Wednesday, October 8, 2014 9:44 PM