A couple weeks ago I patched our CF 9.0.1 production server with APSB11-14, then APSB12-06. We use sandbox security.
About 10 days later, the CF service restarted itself (unsure why) and my users started reporting problems with "blank pages". We determined that it was pages in our applications that have the cfdiv tag in them. Pages appeared blank to the user, but viewing source in the browser reveals a few lines of cfajax output, then nothing. Note that other pages in our app without cfdiv continued to work just fine.
In the \jrun4\logs\cfusion-out.log, this error appears every time we hit a page with cfdiv in it:
error ROOT CAUSE: java.lang.NoClassDefFoundError: Could not initialize class coldfusion.security.ESAPIUtils
There are no errors in the hs_err_pidxxx logs.
I stopped the CF service and restarted it, to no avail. I stopped the CF service again, and thinking the APSB patch might be to blame, renamed the \inetpub\wwwroot\cfide directory and copied the pre-patch backup copy of CFIDE into place. Restarted CF, and all was well it seemed.
CF has been up for about 5 days now, and the error popped up again today. I tried my trick of copying the old "good" CFIDE again, but no such luck this time. Perhaps that was a red herring. I turned off sandbox security and restarted CF, and we are up and running again. I checked the logs and the CF service had restarted itself just before today's "blank page" incident.
System info:
ColdFusion 9.0.1.274733 Enterprise
update level hf901-00003.jar
Java 1.6.0_27
Windows 2003 Enterprise 32-bit
FusionReactor 4.08
Edit: I'm reviewing the \JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\updates and finding the following in the folder:
chf9000001.jar
chf9010001.jar
hf901_00003.jar
According to the technote for APSB12-06, it's jar is hf901_00004.jar, and it says "If hf901-00001.jar, hf901-00002.jar or hf901-00003.jar exist, delete them" so it appears I missed a step.
Question: should I go ahead and install 9.0.1 CHF2 (chf9010002.jar), and then proceed with the APSB12-06 hf901_00004.jar ? Or since CHF2 contains APSB11-14, will that somehow conflict with my previous installation of APSB11-14?
Edit 2: after spending a day reading some tips on Charlie's site, and traversing the folders and understanding how CF updates work, I went ahead and used the "unofficial updater" to bring the system up to date. Now that I think I comprehend the CF updater process, I find it amazing that Adobe doesn't have their own update utility available???? I'll report back in a couple weeks if our issues are solved....