Post reply

excessive amount of connections caused query timeouts

  • March 4, 2009 at 3:02 pm

    #131493

    Recently we have been seeing an issue where all of a sudden the number of connections to the database server doubled and then queries starts timing outs. Once connections dropped, we no longer see timeouts. I am not exactly sure what resources the connections are using on the database server to cause timeouts. I think its memory, but running perfmon, paging counter seems normal. CPU is fine. IO counter was running normal as well. Does someone know why the spike on connections cause query timeouts?

    Thanks much!

    Kathleen

  • March 4, 2009 at 11:54 pm

    #953814

    We had the same issue. Basically you would get query timeout or General Network errors. This happnes when you have website pages that open connection and does not close it. Usually what happens is that the connection pool gets filled up and the websites will stop responding.

    Solving this will take time since you have to make sure all connections are closed even when there is an exception thrown.

    -Roy

  • March 5, 2009 at 7:50 am

    #954043

    Thanks for your response. What I did not understand was what db resource was being taxed on when dealing with so many connections and how I can see it using perfmon, for example.

    Thanks so much!

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply