I have CF 5.0 running on a 1.4GHz 512MB RDRAM Win2K developmnet box.
I've had two instances now where CF 5.0 has gone bonkers and sucked up 100%
of the CPU. Both times, it came after a non-standard shutdown. First time,
we had the power plugged into the non-battery side of the UPS (Duh!) and the
machine went down in a power outage. The next time, I tried to open a Real
Video file while having Spinner.com running. Locked up the machine and had
to turn off power. Now, here is where the CF problem comes in. Upon
re-start, Win2K did it's usual disk check. Then, one of the two running
instances of a process called "ntConsoleJava.e" (the second instance in both
cases) goes hay wire - running the CPU up to 99%. Both times, I tried
everything I knew of to fix the problem, including the "repair" on the CF
5.0 disk. I had to uninstall and reinstall CF 5.0 to solve the problem.
So, is this really a CF issue or an Win2K issue. Yes, I know that it was
first and foremost, a "dumb operator issue" to begin with, but Win2K disk
check should not hose up the "ntConsoleJava.e" file and the
"ntConsoleJava.e" file should be stable enough to handle a non-standard
shutdown. We have not deployed 5.0 on the production box yet, and I'm not
sure we want to until this issue is resolved. Thoughts?
Dave
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
