TechNote (Archived)

Hot fix for possible jvm.config corruption with ColdFusion MX 7.0 or MX 7.0.1 Administrator

Issue

---

Saving changes to the Java and JVM settings screen of the ColdFusion MX 7 Administrator corrupts thecf_root/runtime/bin/jvm.config file. The jvm.config file contains the Java configuration settings that ColdFusion MX uses at runtime. Corruption in this file causes start up errors and server instability.

This issue only affects ColdFusion MX 7 Server configuration.

Note: This issue is fixed in ColdFusion MX 7.0.2.

Reason

---

The ColdFusion MX 7 Administrator save process modifies the-Dcoldfusion.classPath java.arg entry. On Windows platforms, it prepends the path{application.home}/../../classes, to the entry.

This causes ColdFusion MX 7 to throw the error:

 no such classpath element: C:\CFusionMX7\runtime/../../classes 

For Unix platforms, it removes all of the "../" entries in-Dcoldfusion.classPath.

-Dcoldfusion.classPath={application.home}/../lib/updates,{application.home}/../lib,{application.home}/../gateway/lib/,{application.home}/../wwwroot/WEB-INF/cfform/jars

becomes:

-Dcoldfusion.classPath={application.home}/lib/updates,{application.home}/lib,{application.home}/gateway/lib/,{application.home}/wwwroot/WEB-INF/cfform/jars

This causes ColdFusion MX 7 to throw several ClassNotFoundException messages, including:

/opt/coldfusionmx7/runtime/lib/updates: directory does not exist, hotfixes cannot be applied
no such classpath element: /opt/coldfusionmx7/runtime/gateway/lib/
no such classpath element: /opt/coldfusionmx7/runtime/wwwroot/WEB-INF/cfform/jars
java.lang.ClassNotFoundException at coldfusion.bootstrap.BootstrapClassLoader.loadClass(BootstrapClassLoader.java:229)

This has been logged as issue 61605 for ColdFusion MX 7. There is now a hot fix available for ColdFusion MX 7.0.1. This issue does not occur in ColdFusion MX 7.0.2.

Solution

---

There are three solutions for this issue:

• Upgrade to ColdFusion MX 7.0.2.
• Apply the hot fix provided below to ColdFusion MX 7.0.1.
• Manually update your Java settings in the jvm.config file.

Apply hot fix to ColdFusion MX 7.0.1

Adobe has created a hot fix for ColdFusion MX 7.0.1 that resolves this issue.

1. Download the hot fix (59K) and save in {cfwebroot}/CFIDE temporarily.
2. Rename {cfwebroot}/CFIDE/adminapi/runtime.cfc to *.bak
3. Unzip runtime.cfc to {cfwebroot}/CFIDE/adminapi/
4. Confirm the new {cfwebroot}/CFIDE/adminapi/runtime.cfc is present.
5. Delete the downloaded ZIP file from{cfwebroot}/CFIDE.

The final solution, for ColdFusion MX 7.0.1, is to make all Java and JVM changes manually in the jvm.config file. Do not use the ColdFusion MX 7 Administrator, as it will continue to corrupt the file. Perform the following steps to fix the corruption:

1. Stop ColdFusion MX 7.
2. Back up the cf_root/runtime/bin/jvm.config file.
3. Open jvm.config in a text editor.
4. Find the java.args entry.
   • For Windows platforms, remove{application.home}/../../classes, from the-Dcoldfusion.classPath.
   • For Unix platforms, append ../ to each occurrence of {application.home}/ in the-Dcoldfusion.classPath.
5. Save the jvm.config file.
6. Restart ColdFusion MX 7.

Additional Information

---

• ColdFusion hot fixes (MX 7 and higher)

Search Support

---