TechNote

ColdFusion MX 6.1 Updater: Hot fix to improve memory utilization when enabling Debug Logging

Issue

---

In ColdFusion MX 6.1 Updater 1, if you enable debug logging from the ColdFusion MX Administrator console, you may notice a slow memory leak. This becomes more obvious when you enable the debug logging in production or other heavy load situations, for example, QA load testing. This may lead to a "java.lang.OutOfMemory" error.

Reason

---

The behavior is caused by an interaction between ColdFusion MX and the Sun JVM with debug variable data, where the Sun JVM fails to free up the resource.

Solution

---

Macromedia has provided a hot fix for ColdFusion MX 6.1 Updater 1. However, we still highly recommend users not enable debug logging in the production environment or other high load situation for security and performance reasons.

ColdFusion MX 6.1 - Server Configuration

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

1. Download the hot fix (6K).
2. Stop ColdFusion.
3. Create the directory cf_root\runtime\servers\lib if it does not exist.
4. Extract hf59763_611.jar from the downloaded ZIP file, into the following directory:
   cf_root\runtime\servers\lib\
5. Restart ColdFusion.
6. Examine the ColdFusion MX Administrator System Information page and confirm that hf59763_611.jar shows in the Java Class Path list.

Unix

1. Download the hot fix (6K).
2. Stop ColdFusion.
3. Create the directory cf_root/runtime/servers/lib if it does not exist.
4. Extract hf59763_611.jar from the downloaded ZIP file, into the following directory :
   cf_root/runtime/servers/lib/
5. Edit the file cf_root/runtime/bin/jvm.config:
   
   1. Locate the JVM classpath section.
   2. 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 

6. Restart ColdFusion.
7. Examine the ColdFusion MX Administrator System Information page and confirm that hf59763_611.jar shows in the Java Class Path list.

ColdFusion MX 6.1 - J2EE Configuration
ColdFusion MX 6.1 - J2EE Configuration with JRun

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

1. Download the hot fix (6K).
2. Extract hf59763_611.jar from the downloaded ZIP file, into thecf_root/WEB-INF/lib directory.
3. Change the Context Parameter cf.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/hf59763_611.jar,./WEB-INF/cfusion/lib/cfusion.jar
   
   • 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).
4. Stop and restart the J2EE server for changes to take effect.
5. Examine the ColdFusion MX Administrator System Information page and confirm that hot fix hf59763_611.jar shows up in the Version section like 6,1,0 hf59763_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.
6. Repeat steps for each deployed instance of ColdFusion.

About changing the Deployment Descriptor

• 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.

Search Support

---