They are. Problem is, I'm not a Linux guy. Not that I have a dislike of it. Quite the contrary. I have a lot of respect for it and a lot of disdain for Windoze, having learned to deal with Windoze years ago only out of job necessity. I just don't know the Linux environment and the time it'd take me to come up to speed is too much.
I know it's only natural to think in terms of "What've you done for me lately", but keep in mind that until we installed the new webserver, the site was very trouble-free. Even though the old webserver was running at near-capacity for most of every market hour, it was hanging in there. That's saying a lot, especially in a Windoze environment.
Whatever is wrong with this setup is currently eluding detection, but it won't forever.
FWIW, it's throwing an ASP_0147 error. Not a lot of discussion of it on the internet, but what there is seems to point at 3 possibilities, none of which we believe are true here:
1. CPU overloaded. It's not. The peaks are at about 30%.
2. Exceeding configured connection limits. Not the case. We've got it set up to allow unlimited connections. There are only about 1100 connections currently.
3. ASP code not closing connections to the database. I'm unsure about this one and continue to investigate. ASP is *supposed to* close connections on its own at the end of a page, and we've recently gone through the busiest pages and made sure db connections are being closed manually. However, before I get back to SI programming, I'm going to see if there's something I can add to the end of each page that'll programmatically determine what all connections to the db are still open and close them.
Aside from that, there's very little information to be found about this error.
Edit: I've been planning to upgrade this machine to Windoze Server 2003 with IIS6.0, but am not so sure now. One of the discussions I found yesterday about this problem stated that it didn't happen until they did the same upgrade.
AI
