Reply to Timing out?

Forum Index » Website Feedback

Reply to "Timing out?"

Subject:

Emoticons





More smilies

Text Color: Font: Close Marks

[quote=jsteele]Thanks. I'm basically collecting debugging information around the clock. I have been seeing the following issues:

1) errors generated when a nonexistent page is requested. Because of the way the forums are written, this doesn't simply generate a "page not found" error like it normally would. Instead, it generates a Java exception. I had been ignoring these, but because they were filling the log files I started to pay attention. I found that the vast majority either come from spambots or Google's spider. I have no idea why the GoogleBot is trying to index nonexistent pages -- and these aren't pages that once existed but were deleted. They are pages that never existed. Spambots tend to make requests for various php pages that are unlikely to exist on a Java application, to say the least. I think the shear traffic generated by these sources added to the problem and I've taken steps to stop it.  While I was typing this message I saw another of these errors, but it was caused by the BingBot. It tried to retrieve page 28 of a 27 page discussion. The last post in that discussion was in May 2010 and it has never had a page 28. So, why would the BingBot be trying to retrieve it? It makes no sense.

2) search related errors. This is a weird one because it appears that the search system simply crashes very frequently. Yet, I've never had one single complaint about the search crashing -- just a great many complaints that the search system sucks. I can't reproduce the issue myself and I've never seen it with my own eyes. I just see the errors in the logs. I downgraded the search engine this morning in order to see if the errors go away. So far, I haven't seen any of those errors.

3) db connection pool timeouts. This is what I believe is the most important. However, it's also the one that only shows up under heavy load. I have been tweaking pool and db settings for days trying to find a combination that works. So far, no luck.

4) Search Indexing. I think this accounts for the freezes during non-peak hours. When the search indexer starts running, system load goes up. Then, I see a lot of dropped connections as users react to frozen pages and hit "reload".  Then, when the indexer finishes, all sorts of connections come flying in at once which leads to some of the db issues described above. I have also made a couple of changes to the indexer to see if that fixes things. I unexpectedly stumbled across a change that I had made in 2010 that may have contributed to this issue. I reversed that change, so hopefully this will be less of an issue.

I still think there is something else that I am not seeing that is the root cause. If so, I will find it but it might take some time.
[/quote]

Options

	Disable HTML in this message
	Disable BB Code in this message
	Disable smilies in this message

Review message

Search Recent Topics Hottest Topics