Problem with CF dying when related servers under load

[intelwizrd]

We have been dealing with a problem involving a CF server, a SQL server and a Verity server. When either the SQL server or the Verity Server is under load (processors above 80%), the CF service seems to die. It returns a server error and a JRun closed connection message. No additional information, just that message.

All 3 services are on seperate servers
All 3 Servers are running W2k3 Ent
All 3 Servers are Dual Xeon +3GHz w/+4GB RAM and plenty of drive space
CF MX 6.1 with latest updaters and HotFixes (installed in server mode, not a J2EE app)
SQL 2000 Ent SP3a
Verity Full Edition 5.5 (not OEM)
The connections to SQL are done via CF and the connections to Verity are done via a java com object.

We have set the timeout in CF to 20 seconds and it still continues to kill CF when the other servers are under load.

What typically happens is a slight increase in load will occur on the web server, then the sql server or verity server will spike to 100%, then the web server will just die. It never spikes and none of the servers come close to using all of their RAM or even allocated memory.

Any thoughts, this is really starting to drive me up the wall.

----------------------------
Josh
CCNA, MCSE 2003(in progress)

 

[TruthInSatire]

sounds to me like someone is running an extreamly large query produces enough to kill the CF server. i've been known to do this once or twice when the db tries to return a few hundred thousand records to the cf server.



We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.

 

[intelwizrd]

I don't think we have any queries that return that many records or anywhere near that number (i think that the most is somewhere like 400 - 500). I will check though. Initial thought is that there is something more to this.

----------------------------
Josh
CCNA, MCSE 2003(in progress)

 

[ksea]

Also make sure you not storing your sessions in registry. That will end up killing your server as well.