ColdFusion MX 6.1 and MX 6.1 Updater 1: Hot fix for null, null errors

There are various causes for ColdFusion MX to display "null, null" errors. One known issue is corruption of the ColdFusion cookies for cfid or cftoken. These cookies are used for session tracking internally in ColdFusion.

Macromedia issue 45343 identified this specific issue of corrupt or missing cfid/cftoken and was thought resolved with the release of ColdFusion MX 6.1. Additional variants of this issue have been identified since the release of ColdFusion MX 6.1 and ColdFusion MX 6.1 Updater 1. These additional variants have been fixed with the hot fix provided below.

There are other causes for the "null, null" error as well. The most typical issue is that cferror and/or a global site-wide error handler is being used and your application had a NullPointerException (NPE). The simplest way to diagnose this issue is to temporarily remove the cferror code or the site-wide error handler. The next time the error occurs, the underlying error will be shown rather than the "null, null" error.

Follow the instructions below to install the hot fix for ColdFusion MX 6.1 in the server configuration. For J2EE servers including JRun, use the instructions under the J2EE Configuration section.

Windows

Download the appropriate hot fix for your version of ColdFusion:

ColdFusion MX 6.1: hf45343_61.jar(12K)

ColdFusion MX 6.1 Updater 1: hf45343_611.jar(12K)

Stop ColdFusion.

Create the directory cf_root\runtime\servers\lib if it does not exist.

Save the downloaded JAR file into the following directory: cf_root\runtime\servers\lib\.

Restart ColdFusion.

Unix

Download the appropriate hot fix for your version of ColdFusion:

ColdFusion MX 6.1: hf45343_61.jar(12K)

ColdFusion MX 6.1 Updater 1: hf45343_611.jar(12K)

Stop ColdFusion.

Create the directory cf_root/runtime/servers/lib if it does not exist.

Save the downloaded JAR file into the following directory : cf_root/runtime/servers/lib/

Edit the filecf_root/runtime/bin/jvm.config:

Locate the JVM classpath section.

Add {application.home}/runtime/servers/lib as the first entry in the java.class.path list.

For example:

# JVM classpath java.class.path={application.home}/runtime/servers/lib, {application.home}/runtime/../../src, {application.home}/lib/cfusion.jar, {application.home}/runtime/lib/webservices.jar

Restart ColdFusion.

Follow the instructions below to install the hot fix for ColdFusion MX 6.1 in the J2EE configuration with a J2EE server including JRun:

Download the appropriate hot fix for your version of ColdFusion:

ColdFusion MX 6.1: hf45343_61.jar(12K)

ColdFusion MX 6.1 Updater 1: hf45343_611.jar(12K)

Save the downloaded JAR file into thecf_root/WEB-INF/lib directory.

Change the Context Parametercf.class.path

in the Deployment Descriptor (cf_root/WEB-INF/web.xml)

for the Web Application "Macromedia ColdFusion MX" (cfusion.war)

from:

./WEB-INF/cfusion/lib/cfusion.jar

to:

./WEB-INF/lib/hf45343_61.jar,./WEB-INF/cfusion/lib/cfusion.jar (ColdFusion MX 6.1)

OR

./WEB-INF/lib/hf45343_611.jar,./WEB-INF/cfusion/lib/cfusion.jar (ColdFusion MX 6.1 Updater 1)

Note that the two paths in cf.class.path each start with a period and are separated by a comma.
Do not confuse ./WEB-INF/lib (which contains the hot fix jar file) with ./WEB-INF/cfusion/lib (which contains cfusion.jar).

Stop and restart the J2EE server for changes to take effect.

Examine the ColdFusion MX Administrator System Information page and confirm that hf45343_61.jar (ColdFusion MX 6.1) or hf45343_611.jar (ColdFusion MX 6.1 Updater 1) shows up in the Version section like 6,1,0 hf45343_61 or 6,1,0 hf45343_611. Note: You will not see this jar in the Java Class Path because the hot fix jar is being loaded in the Coldfusion Class Path.

Repeat steps for each deployed instance of ColdFusion.

Deployment Descriptor Context Parameters can be changed using the J2EE Administrator Control Panel (WebLogic and JRun) or by using the Application Assembly Tool (Websphere). If your J2EE server does not have such a tool, you must make sure that the Context Parameter change is made for all deployed instances of ColdFusion. It may be necessary to un-deploy CFMX, make the change, then re-deploy CFMX. See your J2EE documentation for other methods.
Be sure to Persist (WebLogic) or Save (Websphere) your changes after you change the value for cf.class.path.
You will usually need to stop and restart your J2EE server to make these changes effective.