Copy link to clipboard
Copied
We have 5 load balanced web servers and we updated two of them to ColdFusion 9.0.1 : Cumulative Hot fix 2 and Coldfusion Security Hotfix APSB11-29 from ColdFusion 9.0.1 : Cumulative Hot fix 1. When the two servers hit heavy load, the CPU maxed out and brought CF to a halt on those machines. In the C:\ColdFusion9\runtime\logs there are timeouts in the logs waiting for an available thread to run.
Server1: coldfusion-out56.log
02/09 09:26:36 Information [scheduler-0] - Run Client Storage Purge
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
Server2- coldfusion-out129.log
02/08 12:42:27 Information [scheduler-0] - Run Client Storage Purge
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
These time outs continuted on until the service was restarted. Has anyone experienced this when they updated to CHF02?
Copy link to clipboard
Copied
I am not at all surprised. There is no such thing as an update from Cumulative Hot fix 1 to Cumulative Hot fix 2!
The rule is, apply only one cumulative update at a time, normally the most recent one. It's all in the word "cumulative". Cumulative Hot fix 2 includes all of CHF1.
My advice is that you should uninstall both CHF1 and CHF2, restart ColdFusion, then re-install CHF02. However, be aware that uninstalling these hot fixes could be quite intricate. They involve updating a large number of ColdFusion's system files.
If you had followed the respective installation instructions for Cumulative Hotfix 1 and Cumulative Hotfix 2, then uninstalling should be straightforward. You will find the instructions at the bottom of those pages.