Uh - first of all: Patch your servers! I hated that philosophy in corporate America and such. Sys Admins telling me they were "anti-patch" because of the existing code set; and they had to spend "time and effort" reverse engineering and testing it. Imagine their surprise with the first CodeRed/Nimda hit.
This always did seem kind of silly - not to jump on the bandwagon, but I highly trust Macromedia to do this testing and release it when they see fit. Why else would I be purchasing their products? If it breaks code, too bad - fix the code. Most likely code that breaks after an updated has been "hacked" in some non-conventional form, anyways. Plus, it's much easier to fix code on a solid app server than a gimped one. Second - High hit and only 500mb of ram??? I HIGHLY suggest you put more RAM in those puppies if it's getting smacked a lot; at the very least a gig or two, maybe more. Most high traffic sites I've seen dedicate one whole gig just for a 'dumb' Apache html/graphic server. Erik Yowell [EMAIL PROTECTED] http://www.shortfusemedia.com -----Original Message----- From: Ezine [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 8:14 PM To: CF-Talk Subject: CFMX Giving up in high strain conditions. Hey This server is pre-updater 1. I'm having an issue with a pair of twin ColdFusionMX (Win2000 Server 500MB RAM, 800Mhz) servers, where CFMX seems to give up when it cannot muster enough system resources..... then when the resources are available.. it is still down and the only way to fix it is to re-start the ColdFusionMX application server service(it appears to just 'give up'). The ColdFusion server can 'give up' in three different ways.. The first way is to simply not return a response(results in a 'can't contact the server' on the client). The second way is to display a blank white page.. <html><head></head><body></body></html>. The third way is to produce a JRUN 404 error. Two specific triggers of this problem as of late are.. Database outages.. and Processor time. This server occasionally fights for processing time with .ASP pages.. ... and an asp page that runs for a while(some times more then 50 seconds(the asp timeout has been removed so that the reports don't error.. the reports take a while.) It would make sense if it simply queued up the requests until the resources became available.. .. but after they become available.. it simply sits there with all the requests in the queue not doing anything. Is this issue resolved in an updater? Has anyone experienced anything similar where coldfusion MX gives up in an extremely high strain environment where Jrun doesn't seem to be doing anything at all(after it gives up)? This is a high hit server with limited resources.. and I'd like to resolve this without 'requiring' that we get another CPU if possible(we will invest in new hardware if there is no other way). -Zine ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
