I'm running ColdFusion MX 6.1 Updater with IIS 5 on a Windows
2000 Server (P4 2.4GHz, 1GB RAM). Recently I decided to install
updates/hotfixes that I'd been behind on (it was running 6.1
without any updates). I installed the 6.1 Updater, then proceeded
to install the hotfixes on this page, minus the ones that didn't
apply (IIS 6, random database fixes): http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=b3a939ce
(everything above 6.1 Updater, of course)
I also modified the JVM arguments and Scheduler arguments as recommeded on this page:
http://www.sargeway.com/blog/index.cfm/2004/10/19/CFMX-Performance
Currently, the JVM arguments are as follows:
Min JVM heap size is set to 256MB, Max is 512MB. I'm running J2SDK 1.4.2_11 (I was running 1.4.2b28 before, or whichever version was distributed with MX 6).
So, the server runs fine for a while, but without any warning, JRUN.EXE starts using 99% of the CPU, and the website is effectively unresponsive. This goes for about 5 minutes, and then JRUN.EXE seems to go back to normal, yet IIS still won't respond to any requests.
When this first happened, I tried stopping and starting the World Wide Web Publishing service, but it was unresponsive. I had to use a third-party utility (pskill) to stop INETINFO.EXE, at which point it restarted automatically, and web pages were served as normal again. If I killed jrun.exe (with the same utility) while it was using all of the CPU, this would also fix the site's issues.
Looking through the logs, the only thing that looks significant around the same time is a few "Connection Reset" entries in \runtime\logs\default-event.log, but these could be due to people hitting Stop because the page is taking too long to load.
What's awesome is that I have a test server configured exactly the same way (same software, same hotfixes, same JVM configuration), all except for the CPU (P3 ~400Mhz), and it hasn't had any problems whatsoever.
So, can anyone give me some insight as to why this might be happening?
I also modified the JVM arguments and Scheduler arguments as recommeded on this page:
http://www.sargeway.com/blog/index.cfm/2004/10/19/CFMX-Performance
Currently, the JVM arguments are as follows:
quote:
-server -Dsun.io.useCanonCaches=false -Xbootclasspath/a:"{application.home}/../lib/webchartsJava2D.jar" -Djavax.xml.parsers.SAXParserFactory=com.macromedia.crimson.jaxp.SAXP arserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=com.macromedia.crimson.jax p.DocumentBuilderFactoryImpl -XX:NewSize=64m -XX:PermSize=32m -XX:MaxPermSize=128m -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC
Min JVM heap size is set to 256MB, Max is 512MB. I'm running J2SDK 1.4.2_11 (I was running 1.4.2b28 before, or whichever version was distributed with MX 6).
So, the server runs fine for a while, but without any warning, JRUN.EXE starts using 99% of the CPU, and the website is effectively unresponsive. This goes for about 5 minutes, and then JRUN.EXE seems to go back to normal, yet IIS still won't respond to any requests.
When this first happened, I tried stopping and starting the World Wide Web Publishing service, but it was unresponsive. I had to use a third-party utility (pskill) to stop INETINFO.EXE, at which point it restarted automatically, and web pages were served as normal again. If I killed jrun.exe (with the same utility) while it was using all of the CPU, this would also fix the site's issues.
Looking through the logs, the only thing that looks significant around the same time is a few "Connection Reset" entries in \runtime\logs\default-event.log, but these could be due to people hitting Stop because the page is taking too long to load.
What's awesome is that I have a test server configured exactly the same way (same software, same hotfixes, same JVM configuration), all except for the CPU (P3 ~400Mhz), and it hasn't had any problems whatsoever.
So, can anyone give me some insight as to why this might be happening?