by Jotapay » Tue 02 Feb 2010, 11:45:49
There are several reasons why this can happen. The web server is basically not responding to requests from your browser.
If the database connections are not being closed in the code and the number of connections increases until the server stops responding, that can do it.
If there is a loop that has not been closed, that can do it.
Memory leaks can do it, but really shouldn't in a robust web server with managed code. It should clean that up by itself.
Log files filling up can do it.
If the database is having problems for some reason (logs, indexes out of whack, partition not sized correctly, searches using too much overhead), that can do it.
Finally, the connection itself between the web server and database itself can become problematic if there are hardware, driver, or firewall issues.
It looks to me like the web server itself is crapping out though. If this is Apache, a quick check of the logs, as long as there is decent error trapping, should tell what is going on.
There are several reasons why this can happen. The web server is basically not responding to requests from your browser.
If the database connections are not being closed in the code and the number of connections increases until the server stops responding, that can do it.
If there is a loop that has not been closed, that can do it.
Memory leaks can do it, but really shouldn't in a robust web server with managed code. It should clean that up by itself.
Log files filling up can do it.
If the database is having problems for some reason (logs, indexes out of whack, partition not sized correctly, searches using too much overhead), that can do it.
Finally, the connection itself between the web server and database itself can become problematic if there are hardware, driver, or firewall issues.
It looks to me like the web server itself is crapping out though. If this is Apache, a quick check of the logs, as long as there is decent error trapping, should tell what is going on.
