Printable View
I have a asp.net 2.0 site that is on a GoDaddy Deluxe hosting package an someone says they keep getting page timeout errors. The site is mostly 2.0 code which has many requests to a MS SQL Server.
The techs on staff disclosed that the package only allows 100 concurrent connections. If it is a concurrent issue, is there a way with code I can view how many connections are made at a given time?
How do you troubleshoot something you can't manage?
Thanks.
Hey,
Your package should include some form of web site tracking application, most hosts do, this should give you an indication of how much traffic you are getting, and at what times.
How busy is your site?
Gary
I guess I am not sure how busy it is but that's what we are trying to figure out. According to Google Analytics, only 72 users were on yesterday when someone notified us of a timeout issue.
I also do get some error emails with the details being:
System.Web.UI.ViewStateException: Invalid viewstate.
I am guessing this error could be from the max concurrent users has been reached and causes the users session to fail.
GoDaddy will not help in providing info on a report that stats when the max has been reached or if there is a way to indicate current connections at a given time.
I guess I could look at my database connections but is there a way to tell if changes are helping? It would be nice to have call that provides you have x connections open so after making changes you can tell if it helped.
Any suggestions?
There are methods that you can use in the Global.asax file, which will allow you to keep a track of the number of open sessions, but these can't really be relied on 100%.
You could also try enabling trace on your web pages to see if that shows up anything.
You might also want to take a dump of the IIS logs for your site, which I am guessing GoDaddy should be able to provide you, and taking a look at that.
Is there anything in the StackTrace of the exception, i.e. what page it is happening on, to shed any light on what is going on.
There are a number of tools that you could use to "stress" your application, in a controlled way, so you can try and replicate a problem. Here is one such tool:
http://blogs.msdn.com/b/alikl/archiv...wcat-tool.aspx
Gary
Gary - thanks for the info. I will see if I can figure out the monitoring tools.
You also say look at the log files. What am I looking for in the log files? Is there a line recorded when the limit has been reached? What should I search for?
No, not exactly, but the log files will show when pages are being accessed, and by which IP Addresses at which time, etc, so you can build up a picture of how many users are on at once.
Gary